Changelog

May 18, 2026

• नया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.
• नया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

• नया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.
• नया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

• नया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.
• नया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.
• नया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.
• नया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.
• सुधरा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.
• सुधरा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.
• सुधरा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.
• सुधराCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• ठीक किया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.
• ठीक कियाअनुपालन निष्कर्ष अब भ्रामक CWE टैग नहीं रखते। पहले legal-compliance check "लापता प्राइवेसी पॉलिसी" और "लापता टर्म्स" निष्कर्षों को CWE-359 (PII एक्सपोज़र) से टैग करता था, जो वास्तविक खामी का वर्णन नहीं करता। ये निष्कर्ष अब बिना CWE के जारी होते हैं — वे अनुपालन आइटम हैं, वर्गीकृत सुरक्षा कमजोरियाँ नहीं।

May 15, 2026

• नया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.
• नयारिपॉज़िटरी सीक्रेट लीक जाँच। GitHub रिपॉज़िटरी स्कैन अब हार्डकोडेड प्रोवाइडर कुंजियों और स्रोत में कमिट किए गए सीक्रेट जैसी उच्च-एंट्रॉपी वैल्यूज़ को फ्लैग कर सकते हैं, सबूत मास्क किए जाते हैं और मानक FixVibe रोटेशन प्रॉम्प्ट शामिल होता है।
• नया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

• नया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.
• नया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.
• सुधरा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

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

• नया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.
• नया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 मई 2026

• सुरक्षा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.
• ठीक किया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.
• सुधराSecurity-header findings केवल root HTML responses पर apply होती हैं। 204, JSON API, file download, या 404 पर missing CSP, Permissions-Policy, X-Frame-Options, या Referrer-Policy अब finding produce नहीं करता। HSTS और X-Content-Type-Options अभी भी सभी responses पर grade होते हैं।
• सुधरा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.
• सुधरा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 मई 2026

• ठीक किया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.
• नयाGitHub repo scans. Repo connect करें और FixVibe source को leaked Supabase service keys, Firebase admin tokens, risky workflow files, और outdated dependencies के लिए check करता है — deployed site load किए बिना। स्कैन प्रकार देखें।
• नयाRisky JavaScript के लिए SAST checks. Repo scans अब new Function() और setTimeout("string") flag करते हैं — untrusted input मिलने पर दोनों eval() के बराबर हैं।
• ठीक कियाVercel / Cloudflare sites पर false “exposed file” findings. Bare 403 Forbidden responses अब “file exists” के रूप में report नहीं होते — ज्यादातर edge providers suspicious-looking paths पर file हो या न हो, 403 return करते हैं। Flag करने से पहले अब हम positive HTTP signal require करते हैं।
• ठीक किया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.
• ठीक कियाlocalStorage में Supabase anon key अब JWT-in-storage finding के रूप में report नहीं होती — anon key publicly-intended client token है। Browser storage में real service-role tokens अब clearer title के साथ critical हैं।
• ठीक किया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.
• ठीक किया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.
• ठीक कियाDomain verification apex ↔ www redirects correctly handle करता है और TXT-record Host field में कौन सा value डालना है, यह ज्यादा clear बताता है।

Format

हर entry tagged है ताकि आप skim कर सकें:

• नया नई check, surface, या feature।
• सुधरा Existing behaviour बेहतर हुआ — ज्यादा accurate, fast, clear।
• ठीक किया एक bug जिसे हमने ship किया और फिर ठीक किया।
• सुरक्षा Hardening, vulnerability fixes, या compliance changes।

कुछ ऐसा दिखा जो टूटा है और यहाँ logged नहीं? support@fixvibe.app पर email करें।