Bokin’ny fanovana

May 18, 2026

• VAOVAOelecterm 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.
• VAOVAOOpenCms 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

• VAOVAOFUXA 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.
• VAOVAOCKAN 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

• VAOVAOPDF.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.
• VAOVAOActive 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.
• VAOVAOSafer 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.
• VAOVAOFirst-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.
• NOHATSARAINAImproved 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.
• NOHATSARAINAImproved 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.
• NOHATSARAINAImproved 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.
• NOHATSARAINACSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• VOAHITSYVercel 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.
• VOAHITSYCompliance 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

• VAOVAOAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• VAOVAOFanaraha-maso ny fivoahan'ny tsiambaratelo amin'ny tahirin-tsoratra. Ny fanadihadiana ny tahirin-tsoratra GitHub dia afaka manamarika lakile mpanome izay nokodirina mafy sy soatoavina mitovy amin'ny tsiambaratelo manana antopia avo izay nampidirina tao amin'ny loharano, miaraka amin'ny porofo voasarona ary ny famporisihana fihodinana FixVibe mahazatra.
• VAOVAOVercel 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

• VAOVAOLiteLLM 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.
• VAOVAOLibreNMS 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.
• NOHATSARAINAFirebase 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

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

• VAOVAORepo 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.
• VAOVAONext.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 Mey 2026

• FIAROVANACross-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.
• VOAHITSYSupabase 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.
• NOHATSARAINAMihatra amin’ny valiny HTML root ihany ny findings security-header. Ny CSP, Permissions-Policy, X-Frame-Options, na Referrer-Policy tsy ampy amin’ny 204, JSON API, file download, na 404 dia tsy mamoaka finding intsony. HSTS sy X-Content-Type-Options mbola asiana grade amin’ny valiny rehetra.
• NOHATSARAINAAuth-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.
• NOHATSARAINAFile-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 Mey 2026

• VOAHITSYThreat-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.
• VAOVAOScan repo GitHub. Ampifandraiso repo iray ary mijery ny source i FixVibe hahitana Supabase service keys tafaporitsaka, Firebase admin tokens, workflow files mampidi-doza, ary dependencies lany andro, nefa tsy mampiditra mihitsy ny site napetrakao. Jereo Karazana scan.
• VAOVAOChecks SAST ho an’ny JavaScript mampidi-doza. Ny repo scans izao dia manamarika new Function() sy setTimeout("string"): samy mitovy amin’ny eval() rehefa omena input tsy atokisana.
• VOAHITSYFindings “exposed file” diso amin’ny sites Vercel / Cloudflare. Tsy tatitra intsony ho “file exists” ny valiny 403 Forbidden tsotra; ny ankamaroan’ny edge providers dia mamerina 403 ho an’ny paths mampiahiahy na misy ilay file na tsia. Mila signal HTTP positive izahay vao manamarika.
• VOAHITSYRepo-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.
• VOAHITSYSupabase anon key ao amin’ny localStorage tsy tatitra intsony ho JWT-in-storage finding: token client natao ho public ny anon key. Ny service-role tokens tena izy ao amin’ny browser storage izao dia critical miaraka amin’ny lohateny mazava kokoa.
• VOAHITSYCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• VOAHITSYReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• VOAHITSYMahazaka tsara redirects apex ↔ www ny fanamarinana domain ary mazava kokoa momba izay sanda apetraka ao amin’ny field Host an’ny TXT-record.

Endrika

Asiana tag ny entry tsirairay mba ho mora vakiana haingana:

• VAOVAO Check, surface, na feature vaovao.
• NOHATSARAINA Nihatsara ny fitondran-tena efa nisy: marina kokoa, haingana kokoa, mazava kokoa.
• VOAHITSY Bug navoakanay ary avy eo nohitsianay.
• FIAROVANA Fanamafisana, fanamboarana vulnerability, na fanovana compliance.

Nahita zavatra simba nefa tsy voasoratra eto? Mandefasa email amin’ny support@fixvibe.app.