Galmee jijjiirraa

May 18, 2026

• HAARAAelecterm 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.
• HAARAAOpenCms 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

• HAARAAFUXA 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.
• HAARAACKAN 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

• HAARAAPDF.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.
• HAARAAActive 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.
• HAARAASafer 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.
• HAARAAFirst-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.
• FOOYYA'EImproved 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.
• FOOYYA'EImproved 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.
• FOOYYA'EImproved 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.
• FOOYYA'ECSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• SIRRAA'EVercel 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.
• SIRRAA'ECompliance 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

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

• HAARAALiteLLM 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.
• HAARAALibreNMS 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.
• FOOYYA'EFirebase 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

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

• HAARAARepo 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.
• HAARAANext.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.

Caamsaa 9, 2026

• NAGEENYACross-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.
• SIRRAA'ESupabase 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.
• FOOYYA'EArgannoowwan security-header deebii root HTML irratti qofa hojiirra oolu. CSP, Permissions-Policy, X-Frame-Options, ykn Referrer-Policy dhabuun 204, JSON API, file download, ykn 404 irratti argannoo hin uumu. HSTS fi X-Content-Type-Options deebii hunda irratti ammas madaalamu.
• FOOYYA'EAuth-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.
• FOOYYA'EFile-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.

Caamsaa 7, 2026

• SIRRAA'EThreat-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.
• HAARAAGitHub repo scans. Repo walitti hidhi, FixVibe source keessatti Supabase service keys miliqan, Firebase admin tokens, workflow files balaa qaban, fi dependencies durii sakatta'a; site deployed kee gonkumaa osoo hin fe'iin. Akaakuu sakatta'iinsaa ilaali.
• HAARAASAST checks JavaScript balaa qabuuf. Repo scans amma new Function() fi setTimeout("string") flag godhu; lamaan isaanii input hin amanamne yoo argatan eval() wajjin walqixa.
• SIRRAA'EFalse “exposed file” findings sites Vercel / Cloudflare irratti. Deebiin 403 Forbidden qofa amma akka “file exists” jedhamee hin gabaafamu; edge providers baay'een paths shakkisiisoo ta'an irratti, faayiliin jiraachuu baatus, 403 deebisu. Flag gochuu dura mallattoo HTTP dhugaa barbaanna.
• SIRRAA'ERepo-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.
• SIRRAA'ESupabase anon key localStorage keessa jiru akka JWT-in-storage finding amma hin gabaafamu; anon key token client uummataaf yaadame dha. Service-role tokens dhugaa browser storage keessa jiran amma critical fi title caalaatti ifa ta'e qabu.
• SIRRAA'ECSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• SIRRAA'EReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• SIRRAA'EDomain verification apex ↔ www redirects sirriitti to'ata, akkasumas gatii kamtu TXT-record Host field keessa akka galu caalaatti ifa godha.

Bifa

Tokkoon tokkoon entry tag qaba akka daftee ilaaluu dandeessuuf:

• HAARAA Check, surface, ykn feature haaraa.
• FOOYYA'E Amalli jiru fooyya'e: caalaatti sirrii, saffisaa, ifa.
• SIRRAA'E Bug nuti erginee booda balleessine.
• NAGEENYA Jabeessa, sirreeffama vulnerability, ykn jijjiirama compliance.

Waan cabee asitti hin galmoofne argitee? Gara support@fixvibe.app email ergi.