Veranderingslog

May 18, 2026

• NUUTelecterm 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.
• NUUTOpenCms 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

• NUUTFUXA 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.
• NUUTCKAN 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

• NUUTPDF.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.
• NUUTActive 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.
• NUUTSafer 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.
• NUUTFirst-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.
• VERBETERImproved 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.
• VERBETERImproved 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.
• VERBETERImproved 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.
• VERBETERCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• REGGESTELVercel 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.
• REGGESTELCompliance 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

• NUUTAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NUUTRepository-geheim-lekkontrole. GitHub-repository-skanderings kan nou hardgekodeerde verskafferssleutels en hoë-entropie geheim-agtige waardes wat na die bron toegewy is, vlag, met bewyse gemaskeer en die standaard FixVibe-rotasie-aanwysing ingesluit.
• NUUTVercel 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

• NUUTLiteLLM 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.
• NUUTLibreNMS 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.
• VERBETERFirebase 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

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

• NUUTRepo 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.
• NUUTNext.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

• SEKURITEITCross-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.
• REGGESTELSupabase 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.
• VERBETERSekuriteitskoptekst-bevindinge geld net vir root-HTML-antwoorde. Ontbrekende CSP, Permissions-Policy, X-Frame-Options, of Referrer-Policy op ’n 204, JSON API, file download, of 404 lewer nie meer ’n bevinding nie. HSTS en X-Content-Type-Options word steeds oor alle antwoorde gegradeer.
• VERBETERAuth-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.
• VERBETERFile-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

• REGGESTELThreat-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.
• NUUTGitHub-repo-skanderings. Koppel ’n repo en FixVibe kontroleer die bron vir gelekte Supabase service keys, Firebase admin tokens, riskante workflow-lêers, en verouderde dependencies; sonder om ooit jou ontplooide webwerf te laai. Sien Skanderingstipes.
• NUUTSAST-kontroles vir riskante JavaScript. Repo-skanderings vlag nou new Function() en setTimeout("string"); albei is gelykstaande aan eval() wanneer hulle onvertroude insette kry.
• REGGESTELVals “exposed file”-bevindinge op Vercel / Cloudflare-webwerwe. Kaal 403 Forbidden-antwoorde word nie meer as “file exists” gerapporteer nie; die meeste edge-verskaffers gee 403 terug vir verdagte paaie of die lêer daar is of nie. Ons vereis nou ’n positiewe HTTP-sein voordat ons vlag.
• REGGESTELRepo-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.
• REGGESTELSupabase anon key in localStorage word nie meer as ’n JWT-in-storage-bevinding gerapporteer nie; die anon key is die publiek-bedoelde kliënttoken. Regte service-role-tokens in blaaierberging is nou critical met ’n duideliker titel.
• REGGESTELCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• REGGESTELReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• REGGESTELDomeinverifikasie hanteer apex ↔ www-redirects korrek en is duideliker oor watter waarde in die TXT-record Host-veld gaan.

Formaat

Elke inskrywing is gemerk sodat jy kan skim:

• NUUT ’n Nuwe kontrole, oppervlak, of funksie.
• VERBETER Bestaande gedrag het beter geword: meer akkuraat, vinniger, duideliker.
• REGGESTEL ’n Fout wat ons verskeep en toe reggemaak het.
• SEKURITEIT Verharding, kwesbaarheidsoplossings, of nakomingsveranderings.

Sien jy iets wat gebreek het en nie hier gelog is nie? Stuur e-pos aan support@fixvibe.app.