වෙනස්කම් ලැයිස්තුව

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.
• නිවැරදි කළ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

• නව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.
• නවRepository secret leak check. GitHub repo scans can now flag hardcoded provider keys and high-entropy secret-like values committed to source, with evidence masked and the standard FixVibe rotation prompt included.
• නව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.

2026 මැයි 9

• ආරක්ෂාව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 එකක් නිපදවන්නේ නැත. 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.

2026 මැයි 7

• නිවැරදි කළ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 deployed site එක කිසිදා load නොකර source එක leaked Supabase service keys, Firebase admin tokens, risky workflow files, සහ outdated dependencies සඳහා check කරයි. Scan types බලන්න.
• නව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 සැක සහිත paths සඳහා file තිබුණත් නැතත් 403 return කරයි. අපි දැන් flag කිරීමට පෙර positive HTTP signal එකක් අවශ්‍ය කරමු.
• නිවැරදි කළ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 දැන් පැහැදිලි 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 නිවැරදිව handle කරන අතර TXT-record Host field තුළ යා යුතු value එක පිළිබඳව වඩා පැහැදිලි වේ.

ආකෘතිය

ඔබට ඉක්මනින් skim කළ හැකි ලෙස සෑම entry එකකටම tag එකක් ඇත:

• නව නව check, surface, හෝ feature එකක්.
• වැඩිදියුණු කළ පවතින behaviour එක වඩා හොඳ විය — වඩා accurate, faster, clearer.
• නිවැරදි කළ අපි ship කර පසුව squash කළ bug එකක්.
• ආරක්ෂාව Hardening, vulnerability fixes, හෝ compliance changes.

මෙහි log කර නැති broken දෙයක් දැක්කාද? support@fixvibe.app වෙත email කරන්න.