Tarihin canje-canje

May 18, 2026

• SABOelecterm 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.
• SABOOpenCms 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

• SABOFUXA 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.
• SABOCKAN 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

• SABOPDF.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.
• SABOActive 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.
• SABOSafer 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.
• SABOFirst-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.
• AN INGANTAImproved 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.
• AN INGANTAImproved 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.
• AN INGANTAImproved 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.
• AN INGANTACSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• AN GYARAVercel 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.
• AN GYARACompliance 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

• SABOAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• SABOBinciken zubar da sirri na ma'ajiyar. Binciken ma'ajiyar GitHub yanzu na iya yiwa alama maɓallan mai bayarwa da aka rubuta a tsararre da kuma manyan ƙimomi masu kama da sirri da aka aiwatar zuwa tushen, tare da shaida da aka rufa-rufe da kuma daidaitaccen umarnin juyawa na FixVibe.
• SABOVercel 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

• SABOLiteLLM 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.
• SABOLibreNMS 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.
• AN INGANTAFirebase 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

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

• SABORepo 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.
• SABONext.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 Mayu, 2026

• TSAROCross-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.
• AN GYARASupabase 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.
• AN INGANTASecurity-header findings suna aiki ne kawai a root HTML responses. Missing CSP, Permissions-Policy, X-Frame-Options, ko Referrer-Policy a 204, JSON API, file download, ko 404 ba sa sake samar da finding. HSTS da X-Content-Type-Options har yanzu ana grade su a duk responses.
• AN INGANTAAuth-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.
• AN INGANTAFile-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 Mayu, 2026

• AN GYARAThreat-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.
• SABOGitHub repo scans. Haɗa repo kuma FixVibe zai duba source don leaked Supabase service keys, Firebase admin tokens, risky workflow files, da outdated dependencies; ba tare da taɓa loda deployed site ɗinka ba. Duba Nau’o’in bincike.
• SABOSAST checks don JavaScript mai haɗari. Repo scans yanzu suna flag new Function() da setTimeout("string"); duka suna daidai da eval() idan an ba su untrusted input.
• AN GYARAFalse “exposed file” findings a kan shafukan Vercel / Cloudflare. Bare 403 Forbidden responses ba a sake rahotonsu a matsayin “file exists” ba; yawancin edge providers suna dawo da 403 ga paths masu kama da tuhuma ko file ɗin yana nan ko babu. Yanzu muna buƙatar positive HTTP signal kafin flagging.
• AN GYARARepo-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.
• AN GYARASupabase anon key a localStorage ba a sake rahotonsa a matsayin JWT-in-storage finding ba; anon key shi ne public-intended client token. Real service-role tokens a browser storage yanzu critical ne tare da title mafi bayyana.
• AN GYARACSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• AN GYARAReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• AN GYARADomain verification yana sarrafa apex ↔ www redirects daidai kuma ya fi bayyana wace value ake sakawa a TXT-record Host field.

Tsari

Kowane shigarwa yana da tag don ka iya leƙawa da sauri:

• SABO Sabon check, surface, ko feature.
• AN INGANTA Halin da ya riga ya wanzu ya inganta: ya fi daidaito, sauri, ko bayyana.
• AN GYARA Kuskuren da muka ship sannan muka gyara.
• TSARO Hardening, gyaran vulnerabilities, ko canje-canjen compliance.

Ka ga wani abu da ya karye kuma ba a rubuta a nan ba? Aika email zuwa support@fixvibe.app.