Wijzigingslog

May 18, 2026

• NIEUWelecterm 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.
• NIEUWOpenCms 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

• NIEUWFUXA 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.
• NIEUWCKAN 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

• NIEUWPDF.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.
• NIEUWActive 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.
• NIEUWSafer 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.
• NIEUWFirst-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.
• VERBETERDImproved 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.
• VERBETERDImproved 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.
• VERBETERDImproved 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.
• VERBETERDCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• OPGELOSTVercel 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.
• OPGELOSTCompliance-bevindingen dragen geen misleidende CWE-tags meer. De legal-compliance-check tagde "ontbrekend privacybeleid" en "ontbrekende voorwaarden" eerder met CWE-359 (PII-blootstelling), wat het werkelijke hiaat niet beschrijft. Deze bevindingen worden nu zonder CWE gepubliceerd — het zijn compliance-items, geen classificeerbare beveiligingszwakheden.

May 15, 2026

• NIEUWAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NIEUWRepository-secret-lekcontrole. GitHub-repositoryscans kunnen nu hardgecodeerde providersleutels en hoog-entropie geheim-achtige waarden in de broncode markeren, met gemaskeerde bewijslast en de standaard FixVibe-rotatieprompt erbij.
• NIEUWVercel 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

• NIEUWLiteLLM 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.
• NIEUWLibreNMS 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.
• VERBETERDFirebase 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

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

• NIEUWRepo 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.
• NIEUWNext.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 mei 2026

• BEVEILIGINGCross-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.
• OPGELOSTSupabase 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.
• VERBETERDSecurity-header findings gelden alleen voor root HTML responses. Een ontbrekende CSP, Permissions-Policy, X-Frame-Options of Referrer-Policy op een 204, JSON API, file download of 404 produceert geen bevinding meer. HSTS en X-Content-Type-Options worden nog steeds over alle responses beoordeeld.
• VERBETERDAuth-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.
• VERBETERDFile-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 mei 2026

• OPGELOSTThreat-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.
• NIEUWGitHub-repo-scans. Verbind een repo en FixVibe checkt de source op gelekte Supabase service keys, Firebase admin tokens, riskante workflow files en verouderde dependencies — zonder ooit je gedeployde site te laden. Zie Scantypen.
• NIEUWSAST-checks voor riskante JavaScript. Repo-scans flaggen nu new Function() en setTimeout("string") — allebei equivalent aan eval() wanneer ze untrusted input krijgen.
• OPGELOSTValse “exposed file”-bevindingen op Vercel / Cloudflare-sites. Kale 403 Forbidden-responses worden niet meer gerapporteerd als “file exists” — de meeste edge providers geven 403 terug voor verdacht ogende paden, of het bestand nu bestaat of niet. We vereisen nu een positief HTTP-signaal voordat we flaggen.
• OPGELOSTRepo-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.
• OPGELOSTSupabase anon key in localStorage wordt niet langer gerapporteerd als JWT-in-storage finding — de anon key is de publiek bedoelde client token. Echte service-role tokens in browser storage zijn nu critical met een duidelijkere titel.
• OPGELOSTCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• OPGELOSTReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• OPGELOSTDomeinverificatie behandelt apex ↔ www redirects correct en is duidelijker over welke waarde in het Host-veld van het TXT-record moet.

Formaat

Elke entry is getagd zodat je snel kunt scannen:

• NIEUW Een nieuwe check, surface of feature.
• VERBETERD Bestaand gedrag is beter geworden — nauwkeuriger, sneller, duidelijker.
• OPGELOST Een bug die we shipten en daarna hebben opgelost.
• BEVEILIGING Hardening, kwetsbaarheidsfixes of compliance-wijzigingen.

Zie je iets dat stuk is en hier niet staat? Mail support@fixvibe.app.