Changelog

May 18, 2026

• ỌHỤRỤ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.
• ỌHỤRỤ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

• ỌHỤRỤ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.
• ỌHỤRỤ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

• ỌHỤRỤ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.
• ỌHỤRỤ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.
• ỌHỤRỤ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.
• ỌHỤRỤ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.
• MMAWANYEImproved 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.
• MMAWANYEImproved 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.
• MMAWANYEImproved 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.
• MMAWANYECSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• EMEZIRIVercel 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.
• EMEZIRICompliance 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

• ỌHỤRỤ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.
• ỌHỤRỤNlebanya ndèpụta ihe nzuzo nke ụlọ akwụkwọ. Nyochaa ụlọ akwụkwọ GitHub nwere ike ugbu a igosipụta igodo ndị na-enye onye ji koodu siri ike na uru dị elu dị ka ihe nzuzo nke etinyere n'isi mmalite, na ihe àmà kpuchiri na ngwa ọkwa ntụgharị FixVibe.
• ỌHỤRỤ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

• ỌHỤRỤ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.
• ỌHỤRỤ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.
• MMAWANYEFirebase 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

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

• ỌHỤRỤ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.
• ỌHỤRỤ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.

May 9, 2026

• NCHEKWACross-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.
• EMEZIRISupabase 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.
• MMAWANYESecurity-header findings na-emetụta naanị root HTML responses. CSP, Permissions-Policy, X-Frame-Options, ma ọ bụ Referrer-Policy na-efu na 204, JSON API, file download, ma ọ bụ 404 anaghị emepụta finding ọzọ. HSTS na X-Content-Type-Options ka na-grade responses niile.
• MMAWANYEAuth-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.
• MMAWANYEFile-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.

May 7, 2026

• EMEZIRIThreat-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.
• ỌHỤRỤGitHub repo scans. Jikọọ repo, FixVibe ga-ele source anya maka leaked Supabase service keys, Firebase admin tokens, workflow files dị ize ndụ, na dependencies ochie — na-enweghị ibunye deployed site gị. Lee Ụdị scan.
• ỌHỤRỤSAST checks maka JavaScript dị ize ndụ. Repo scans ugbu a na-flag new Function() na setTimeout("string") — ha abụọ hà ka eval() mgbe e nyere ha untrusted input.
• EMEZIRIFalse “exposed file” findings na Vercel / Cloudflare sites. Bare 403 Forbidden responses anaghịzi apụta dịka “file exists” — ọtụtụ edge providers na-alaghachi 403 maka paths na-ele suspicious ma file ahụ dị ma ọ bụ na ọ dịghị. Anyị chọrọ positive HTTP signal ugbu a tupu flagging.
• EMEZIRIRepo-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.
• EMEZIRISupabase anon key na localStorage anaghịzi apụta dịka JWT-in-storage finding — anon key bụ public client token e zubere. Real service-role tokens na browser storage ugbu a bụ critical nwere title doro anya karịa.
• EMEZIRICSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• EMEZIRIReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• EMEZIRIDomain verification na-ejikwa apex ↔ www redirects nke ọma ma na-akọwa nke ọma value ga-abanye na TXT-record Host field.

Format

Entry ọ bụla nwere tag ka ị nwee ike skim:

• ỌHỤRỤ Check, surface, ma ọ bụ feature ọhụrụ.
• MMAWANYE Behaviour dị adị ghọrọ mma — ziri ezi karịa, ngwa ngwa karịa, doo anya karịa.
• EMEZIRI Bug anyị ship wee kpochapụ.
• NCHEKWA Hardening, vulnerability fixes, ma ọ bụ compliance changes.

Ị hụrụ ihe mebiri ma na-adịghị logged ebe a? Zipu email na support@fixvibe.app.