FixVibe

// docs / changelog

Dəyişiklik jurnalı

FixVibe scan-engine updates: new coverage, safety improvements, and accuracy improvements. Newest entries first.

May 18, 2026

  • YENİ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.
  • YENİ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

  • YENİ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.
  • YENİ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

  • YENİ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.
  • YENİ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.
  • YENİ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.
  • YENİ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.
  • YAXŞILAŞDIRILDIImproved 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.
  • YAXŞILAŞDIRILDIImproved 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.
  • YAXŞILAŞDIRILDIImproved 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.
  • YAXŞILAŞDIRILDICSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
  • DÜZƏLDİLDİ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.
  • DÜZƏLDİLDİ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

  • YENİ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.
  • YENİRepozitor sirr sızması yoxlanışı. GitHub repozitor skanları indi mənbəyə yerləşdirilmiş sərt kodlanmış provayder açarlarını və yüksək entropiyalı sirr bənzəri dəyərləri qeyd edə bilər, sübut maskalanır və standart FixVibe növbə təlimatı daxil edilir.
  • YENİ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

  • YENİ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.
  • YENİ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.
  • YAXŞILAŞDIRILDIFirebase 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

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

  • YENİ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.
  • YENİ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 may 2026

  • TƏHLÜKƏSİZLİKCross-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.
  • DÜZƏLDİLDİ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.
  • YAXŞILAŞDIRILDISecurity-header findings yalnız root HTML responses üçün tətbiq olunur. 204, JSON API, file download və ya 404 üzərində Missing CSP, Permissions-Policy, X-Frame-Options və ya Referrer-Policy artıq finding yaratmır. HSTS və X-Content-Type-Options hələ də bütün responses üzrə grade edir.
  • YAXŞILAŞDIRILDIAuth-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.
  • YAXŞILAŞDIRILDIFile-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 may 2026

  • DÜZƏLDİLDİ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.
  • YENİGitHub repo scans. Repo qoşun və FixVibe deployed site-ınızı yükləmədən source-u leaked Supabase service keys, Firebase admin tokens, risky workflow files və outdated dependencies üçün yoxlayır. Baxın Skan növləri.
  • YENİRiskli JavaScript üçün SAST checks. Repo scans indi new Function()setTimeout("string") flag edir — hər ikisi untrusted input ilə qidalananda eval()-a bərabərdir.
  • DÜZƏLDİLDİVercel / Cloudflare sites üzərində false “exposed file” findings. Bare 403 Forbidden responses artıq “file exists” kimi reported deyil — edge providers-in çoxu suspicious-looking paths üçün file olub-olmamasından asılı olmayaraq 403 qaytarır. İndi flag etməzdən əvvəl positive HTTP signal tələb edirik.
  • DÜZƏLDİLDİ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.
  • DÜZƏLDİLDİlocalStorage-də Supabase anon key artıq JWT-in-storage finding kimi reported deyil — anon key publicly-intended client token-dir. Browser storage-də real service-role tokens indi daha aydın title ilə critical-dır.
  • DÜZƏLDİLDİ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.
  • DÜZƏLDİLDİ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.
  • DÜZƏLDİLDİDomain verification apex ↔ www redirects-i düzgün handles edir və TXT-record Host field-ə hansı value-nun yazılmalı olduğunu daha aydın göstərir.

Format

Hər entry tag-lənib ki, tez gözdən keçirə biləsiniz:

  • YENİ Yeni check, surface və ya feature.
  • YAXŞILAŞDIRILDI Existing behaviour yaxşılaşıb — daha accurate, faster, clearer.
  • DÜZƏLDİLDİ Ship etdiyimiz və sonra squashed etdiyimiz bug.
  • TƏHLÜKƏSİZLİK Hardening, vulnerability fixes və ya compliance changes.

Nəsə qırılıb və burada logged deyil? support@fixvibe.app-ə email yazın.

Dəyişiklik jurnalı — Docs · FixVibe