Рӯйхати тағйирот

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.
• НАВMagicMirror /cors SSRF check. Verified active scans can now confirm CVE-2026-42281 exposure on MagicMirror instances when the unauthenticated /cors endpoint fetches a FixVibe-controlled external callback, without probing internal services.

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.

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 мешаванд. Missing CSP, Permissions-Policy, X-Frame-Options ё Referrer-Policy дар 204, JSON API, file download ё 404 дигар finding намедиҳад. HSTS ва X-Content-Type-Options ҳанӯз across all 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 месанҷад — бе он ки deployed site-и шуморо load кунад. Нигаред Scan types.
• НАВSAST checks барои JavaScript-и risky. Repo scans акнун new Function() ва setTimeout("string")-ро flag мекунанд — ҳар ду вақте untrusted input дода шавад, ба eval() баробаранд.
• ИСЛОҲШУДАFalse “exposed file” findings дар Vercel / Cloudflare sites. Bare 403 Forbidden responses дигар ҳамчун “file exists” report намешаванд — аксари edge providers барои path-ҳои suspicious-looking 403 медиҳанд, хоҳ file бошад ё не. Мо акнун пеш аз flagging 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.
• ИСЛОҲШУДАSupabase anon key дар localStorage дигар ҳамчун JWT-in-storage finding report намешавад — anon key client token-и publicly-intended аст. Real service-role tokens дар browser storage акнун critical бо title-и равшантар ҳастанд.
• ИСЛОҲШУДА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 redirect-ҳои apex ↔ www-ро дуруст handle мекунад ва равшантар мегӯяд, ки кадом value ба field-и TXT-record Host меравад.

Формат

Ҳар entry tag дорад, то зуд skim кунед:

• НАВ Check, surface ё feature-и нав.
• БЕҲТАРШУДА Behaviour-и мавҷуда беҳтар шуд — accurate-тар, тезтар, равшантар.
• ИСЛОҲШУДА Bug-е, ки ship кардем ва баъд squashed кардем.
• АМНИЯТ Hardening, vulnerability fixes ё compliance changes.

Чизеро дидед, ки шикастааст ва ин ҷо logged нест? Ба support@fixvibe.app email фиристед.