Üýtgeşmeler sanawy

May 18, 2026

• TÄZEelecterm 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.
• TÄZEOpenCms 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

• TÄZEFUXA 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.
• TÄZECKAN 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

• TÄZEPDF.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.
• TÄZEActive 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.
• TÄZESafer 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.
• TÄZEFirst-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.
• GOWULANDYImproved 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.
• GOWULANDYImproved 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.
• GOWULANDYImproved 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.
• GOWULANDYCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• DÜZEDILDIVercel 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ÜZEDILDICompliance 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

• TÄZEAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• TÄZERepository 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.
• TÄZEVercel 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

• TÄZELiteLLM 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.
• TÄZELibreNMS 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.
• GOWULANDYFirebase 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

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

• TÄZERepo 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.
• TÄZENext.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-njy ýylyň 9-njy maýy

• HOWPSUZLYKCross-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ÜZEDILDISupabase 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.
• GOWULANDYSecurity-header findings diňe root HTML responses-a apply bolýar. 204, JSON API, file download ýa-da 404 üstünde missing CSP, Permissions-Policy, X-Frame-Options ýa-da Referrer-Policy indi finding döretmeýär. HSTS we X-Content-Type-Options henizem ähli responses boýunça grade edýär.
• GOWULANDYAuth-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.
• GOWULANDYFile-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-njy ýylyň 7-nji maýy

• DÜZEDILDIThreat-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.
• TÄZEGitHub repo scans. Repo connect ediň we FixVibe deployed site-iňizi hiç haçan load etmän source içinde leaked Supabase service keys, Firebase admin tokens, risky workflow files we outdated dependencies barlaýar. Serediň Scan types.
• TÄZERiskli JavaScript üçin SAST checks. Repo scans indi new Function() we setTimeout("string") flag edýär — ikisi hem untrusted input berlende eval() bilen deň.
• DÜZEDILDIVercel / Cloudflare sites üstünde ýalan “exposed file” findings. Bare 403 Forbidden responses indi “file exists” hökmünde report edilmeýär — edge providers köpüsi suspicious-looking paths üçin file bar-barligine garamazdan 403 berýär. Flagging-den öň indi positive HTTP signal talap edýäris.
• DÜZEDILDIRepo-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ÜZEDILDIlocalStorage içindäki Supabase anon key indi JWT-in-storage finding hökmünde report edilmeýär — anon key publicly-intended client token. Browser storage-daky real service-role tokens indi has aýdyň title bilen critical.
• DÜZEDILDICSP 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ÜZEDILDIReflected-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ÜZEDILDIDomain verification apex ↔ www redirects-i dogry handle edýär we TXT-record Host field içine haýsy value goýulýandygyny has aýdyň görkezýär.

Format

Her entry tag edilen, çalt skim edip bilersiňiz:

• TÄZE Täze check, surface ýa-da feature.
• GOWULANDY Bar bolan behaviour gowulaşdy — has accurate, has çalt, has aýdyň.
• DÜZEDILDI Ship edilen, soň bolsa squashed edilen bug.
• HOWPSUZLYK Hardening, vulnerability fixes ýa-da compliance changes.

Döwlen, ýöne bu ýerde logged däl zat gördüňizmi? support@fixvibe.app salgysyna email iberiň.