Zoznam zmien

May 18, 2026

• NOVÉelecterm 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.
• NOVÉOpenCms 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

• NOVÉFUXA 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.
• NOVÉCKAN 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

• NOVÉPDF.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.
• NOVÉActive 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.
• NOVÉSafer 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.
• NOVÉFirst-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.
• ZLEPŠENÉImproved 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.
• ZLEPŠENÉImproved 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.
• ZLEPŠENÉImproved 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.
• ZLEPŠENÉCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• OPRAVENÉVercel 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.
• OPRAVENÉCompliance findings no longer carry misleading CWE tags. The legal-compliance check previously tagged "missing privacy policy" and "missing terms of service" findings with CWE-359 (PII exposure), which doesn't describe the actual gap. Those findings now ship without a CWE — they're compliance/governance items, not classifiable security weaknesses.

May 15, 2026

• NOVÉAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NOVÉRepository secret leak check. GitHub repo scans can now flag hardcoded provider keys and high-entropy secret-like values committed to source, with evidence masked and the standard FixVibe rotation prompt included.
• NOVÉVercel 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

• NOVÉLiteLLM 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.
• NOVÉLibreNMS 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.
• ZLEPŠENÉFirebase 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

• NOVÉRepo 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.
• NOVÉSupabase Storage posture check. Passive scans can now review public Supabase Storage buckets and anonymous object-listing exposure alongside existing RLS and key checks.
• NOVÉAI-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

• NOVÉRepo 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.
• NOVÉNext.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. mája 2026

• BEZPEČNOSŤCross-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.
• OPRAVENÉSupabase 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.
• ZLEPŠENÉNálezy bezpečnostných hlavičiek sa vzťahujú iba na root HTML odpovede. Chýbajúce CSP, Permissions-Policy, X-Frame-Options alebo Referrer-Policy na 204, JSON API, sťahovaní súboru alebo 404 už nevytvorí nález. HSTS a X-Content-Type-Options sa stále hodnotia naprieč všetkými odpoveďami.
• ZLEPŠENÉAuth-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.
• ZLEPŠENÉFile-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. mája 2026

• OPRAVENÉThreat-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.
• NOVÉSkeny GitHub repozitárov. Pripoj repo a FixVibe skontroluje zdroj na uniknuté Supabase service keys, Firebase admin tokeny, rizikové workflow súbory a zastarané závislosti, bez toho, aby vôbec načítal tvoj nasadený web. Pozri Typy skenovania.
• NOVÉSAST kontroly rizikového JavaScriptu. Repo skeny teraz označujú new Function() a setTimeout("string"), obe sú pri nedôveryhodnom vstupe ekvivalentné eval().
• OPRAVENÉFalošné nálezy “exposed file” na Vercel / Cloudflare weboch. Holé odpovede 403 Forbidden sa už nehlásia ako “file exists”, väčšina edge providerov vracia 403 pre podozrivo vyzerajúce cesty bez ohľadu na to, či súbor existuje. Pred označením teraz vyžadujeme pozitívny HTTP signál.
• OPRAVENÉRepo-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.
• OPRAVENÉSupabase anon key v localStorage sa už nehlási ako JWT-in-storage nález, anon key je verejne určený klientsky token. Skutočné service-role tokeny v browser storage sú teraz critical s jasnejším názvom.
• OPRAVENÉCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• OPRAVENÉReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• OPRAVENÉOverenie domény správne zvláda apex ↔ www redirecty a jasnejšie vysvetľuje, ktorá hodnota patrí do poľa Host v TXT zázname.

Formát

Každý záznam má tag, aby sa dal rýchlo preletieť:

• NOVÉ Nová kontrola, povrch alebo funkcia.
• ZLEPŠENÉ Existujúce správanie sa zlepšilo: presnejšie, rýchlejšie alebo jasnejšie.
• OPRAVENÉ Chyba, ktorú sme vydali a potom opravili.
• BEZPEČNOSŤ Spevnenie, opravy zraniteľností alebo compliance zmeny.

Všimol si si niečo, čo sa pokazilo a nie je tu zapísané? Napíš na support@fixvibe.app.