Changelog

May 18, 2026

• NUOVOelecterm dependency advisory check. GitHub repo scans can now flag npm manifests and lockfiles that pin or allow electerm versions affected by CVE-2026-41500 / GHSA-wxw2-rwmh-vr8f, with version-based advisory evidence rather than exploit confirmation.
• NUOVOOpenCms dependency advisory check. GitHub repo scans can now flag Maven pom.xml files that pin or resolve org.opencms:opencms-core versions affected by CVE-2023-42344 / GHSA-rcc6-6q2f-m2cw, with version-based advisory evidence rather than XXE exploit confirmation.

May 17, 2026

• NUOVOFUXA hardcoded JWT secret check. Verified active scans can now confirm CVE-2025-69971 exposure on FUXA instances that still trust the vulnerable fallback JWT signing configuration.
• NUOVOCKAN DataStore SQL exposure check. Verified active scans can now confirm unauthenticated CKAN DataStore SQL access associated with CVE-2026-42031 and guide teams to patched CKAN release lines or safer DataStore configuration.

16 May 2026

• NUOVOPDF.js dependency advisory check. GitHub repo scans can now flag npm manifests and lockfiles that pin or allow pdfjs-dist versions affected by CVE-2024-4367 / GHSA-wgrm-67xf-hhpq.
• NUOVOActive scans via REST API and MCP. Active scans can now be triggered from REST and MCP against verified domains that have been explicitly authorized from the dashboard. Authorization is revocable at any time.
• NUOVOSafer authorization levels for active scans. Domain authorization now distinguishes safer automated active checks from deeper active testing, so teams can automate the right level of verification for each domain.
• NUOVOFirst-use webhook for API/MCP active scans. A webhook can notify teams the first time an API/MCP-triggered active scan runs against a newly authorized domain.
• MIGLIORATOImproved Referrer-Policy findings. Missing or weak Referrer-Policy results now separate URL-referrer leakage from broad information exposure, show document-response evidence, and include generic plus static-host remediation guidance.
• MIGLIORATOImproved Permissions-Policy findings. Missing or weak Permissions-Policy results now show feature-level evidence, separate broad feature allowlists from missing hardening, and include generic plus static-host remediation guidance for common hosts, proxies, and app servers.
• MIGLIORATOImproved clickjacking header prompts. Missing X-Frame-Options findings now point agents to CSP frame-ancestors as the modern protection, add Vercel/static SPA header guidance, and verify x-frame-options with CSP.
• MIGLIORATOCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• CORRETTOVercel path-probe false positives reduced. FixVibe now requires stronger application-specific evidence before reporting exposed framework artifacts on deployments that rewrite unknown routes to the app shell.
• CORRETTOI rilevamenti di conformità non riportano più tag CWE fuorvianti. Il check legal-compliance assegnava CWE-359 (esposizione di PII) a "informativa privacy mancante" e "termini mancanti", che non descrive il vero gap. Ora vengono pubblicati senza CWE — sono questioni di conformità, non debolezze di sicurezza classificabili.

May 15, 2026

• NUOVOAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NUOVOVerifica fuga di segreti nel repository. Le scansioni di repository GitHub possono ora segnalare chiavi di provider hardcoded e valori ad alta entropia simili a segreti committati nel codice, con le prove mascherate e il prompt di rotazione standard di FixVibe incluso.
• NUOVOVercel deployment protection check. Passive scans can now flag public *.vercel.app generated deployment URLs that respond without Vercel Deployment Protection, while existing header checks continue to audit CSP, HSTS, and browser hardening.

May 14, 2026

• NUOVOLiteLLM dependency advisory check. GitHub repo scans can now flag Python dependency files that pin or allow LiteLLM versions affected by CVE-2026-42208 / GHSA-r75f-5x8p-qvmc.
• NUOVOLibreNMS dependency advisory check. GitHub repo scans can now flag Composer manifests that pin or allow LibreNMS versions affected by CVE-2024-51092 / GHSA-x645-6pf9-xwxw.
• MIGLIORATOFirebase rules detection improved. BaaS scans now detect more Firebase app shapes and use read-only evidence to identify risky public data exposure.

May 13, 2026

• NUOVORepo Supabase RLS migration check. GitHub repo scans can now flag Supabase SQL migrations that create public tables without a matching ALTER TABLE ... ENABLE ROW LEVEL SECURITY statement.
• NUOVOSupabase Storage posture check. Passive scans can now review public Supabase Storage buckets and anonymous object-listing exposure alongside existing RLS and key checks.
• NUOVOAI-generated code guardrail check. GitHub repo scans can now flag missing security automation around code scanning, secret scanning, dependency updates, and AI-agent instructions.

May 12, 2026

• NUOVORepo web-app risk checklist. GitHub repo scans can now flag high-confidence OWASP-style code risks such as raw SQL interpolation, unsafe HTML sinks, credentialed wildcard CORS, disabled TLS verification, and weak JWT secret fallbacks.
• NUOVONext.js middleware-bypass check. Active scans for verified domains can now confirm CVE-2025-29927 exposure on middleware-protected routes before reporting it, and reports include the standard FixVibe AI fix prompt for remediation.

9 maggio 2026

• SICUREZZACross-origin scope hardening. Active scans and client-asset checks now stay within the authorized target scope and avoid carrying customer-provided credentials across cross-origin redirects.
• CORRETTOSupabase RLS check is now strictly read-only. Supabase posture checks now avoid write attempts and focus on safe exposure signals. Verified-domain active testing remains the boundary for deeper confirmation.
• MIGLIORATOLe segnalazioni sugli header di sicurezza si applicano solo alle risposte HTML root. CSP, Permissions-Policy, X-Frame-Options o Referrer-Policy mancanti su un 204, un'API JSON, un download di file o una 404 non producono più una segnalazione. HSTS e X-Content-Type-Options continuano a essere valutati su tutte le risposte.
• MIGLIORATOAuth-flow and rate-limit checks now require stronger evidence. FixVibe now reports these issues only when the application behavior clearly supports the finding, reducing noise from generic error pages and unsupported methods.
• MIGLIORATOFile-upload findings tier by exploitability evidence. File-upload reports now separate low-confidence acceptance signals from stronger evidence of risky serving behavior, reducing over-severity on benign upload handlers.

7 maggio 2026

• CORRETTOThreat-intel listing accuracy improved. FixVibe now distinguishes real blocklist evidence from resolver diagnostics so threat-intel findings do not over-report on infrastructure-side lookup responses.
• NUOVOScansioni di repository GitHub. Collega un repo e FixVibe controlla il sorgente per chiavi service Supabase esposte, token admin Firebase, file workflow rischiosi e dipendenze obsolete, senza mai caricare il tuo sito distribuito. Vedi Tipi di scansione.
• NUOVOCheck SAST per JavaScript rischioso. Le scansioni repo ora segnalano new Function() e setTimeout("string"): entrambi equivalgono a eval() quando ricevono input non attendibile.
• CORRETTOFalse segnalazioni “file esposto” su siti Vercel / Cloudflare. Le semplici risposte 403 Forbidden non sono più segnalate come “file exists”: la maggior parte dei provider edge restituisce 403 per path dall'aspetto sospetto, che il file esista o meno. Ora richiediamo un segnale HTTP positivo prima di segnalare.
• CORRETTORepo-code false positives reduced. Repo scans now avoid flagging security terms in comments, documentation, test helpers, and clearly server-only contexts for several high-signal code checks.
• CORRETTOLa chiave anon Supabase in localStorage non viene più segnalata come finding JWT-in-storage: la chiave anon è il token client previsto come pubblico. I veri token service-role nello storage del browser ora sono critical con un titolo più chiaro.
• CORRETTOCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• CORRETTOReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• CORRETTOLa verifica del dominio gestisce correttamente i redirect apex ↔ www ed è più chiara su quale valore inserire nel campo Host del record TXT.

Formato

Ogni voce è etichettata così puoi scorrerla rapidamente:

• NUOVO Un nuovo check, superficie o funzionalità.
• MIGLIORATO Un comportamento esistente è migliorato: più accurato, più veloce, più chiaro.
• CORRETTO Un bug che abbiamo rilasciato e poi corretto.
• SICUREZZA Hardening, correzioni di vulnerabilità o modifiche di conformità.

Noti qualcosa che si è rotto e non è registrato qui? Scrivi a support@fixvibe.app.