Log atharrachaidhean

May 18, 2026

• ÙRelecterm 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.
• ÙROpenCms 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

• ÙRFUXA 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.
• ÙRCKAN 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

• ÙRPDF.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.
• ÙRActive 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.
• ÙRSafer 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.
• ÙRFirst-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.
• LEASAICHTEImproved 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.
• LEASAICHTEImproved 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.
• LEASAICHTEImproved 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.
• LEASAICHTECSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• CEARTAICHTEVercel 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.
• CEARTAICHTECompliance 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

• ÙRAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• ÙRSgrùdadh aoidion dìomhaireachd taisgealan. Faodaidh sganaidhean taisgealan GitHub a-nis bratach a chur air iuchraichean solaraiche le còd cruaidh agus luachan coltach ri dìomhaireachd le àrd-eantropaidh a chaidh a chur dhan stòr-obrach, le fianais air a fhalach agus an cuiridh cuairteachadh àbhaisteach FixVibe na ghabhail a-steach.
• ÙRVercel 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

• ÙRLiteLLM 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.
• ÙRLibreNMS 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.
• LEASAICHTEFirebase 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

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

• ÙRRepo 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.
• ÙRNext.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 Cèitean, 2026

• TÈARAINTEACHDCross-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.
• CEARTAICHTESupabase 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.
• LEASAICHTEChan eil security-header findings a' buntainn ach ri root HTML responses. Cha chruthaich CSP, Permissions-Policy, X-Frame-Options, no Referrer-Policy a dhìth air 204, JSON API, file download, no 404 finding tuilleadh. Tha HSTS agus X-Content-Type-Options fhathast a' grade thar gach response.
• LEASAICHTEAuth-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.
• LEASAICHTEFile-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 Cèitean, 2026

• CEARTAICHTEThreat-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.
• ÙRGitHub repo scans. Ceangail repo agus nì FixVibe check air an source airson leaked Supabase service keys, Firebase admin tokens, risky workflow files, agus outdated dependencies — gun do deployed site a loading a-riamh. Faic Seòrsaichean scan.
• ÙRSAST checks airson JavaScript risky. Tha repo scans a-nis a' flag new Function() agus setTimeout("string") — tha an dà chuid equivalent to eval() nuair a gheibh iad untrusted input.
• CEARTAICHTEFalse “exposed file” findings air làraichean Vercel / Cloudflare. Chan eil bare 403 Forbidden responses air an aithris tuilleadh mar “file exists” — tillidh a' mhòr-chuid de edge providers 403 airson paths a tha a' coimhead amharasach ge bith a bheil am file ann no nach eil. Tha sinn a-nis ag iarraidh positive HTTP signal mus flag sinn.
• CEARTAICHTERepo-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.
• CEARTAICHTEChan eil Supabase anon key ann an localStorage air aithris tuilleadh mar JWT-in-storage finding — 's e an anon key an client token a tha poblach a dh'aona-ghnothach. Tha real service-role tokens ann am browser storage a-nis critical le title nas soilleire.
• CEARTAICHTECSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• CEARTAICHTEReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• CEARTAICHTELàimhsichidh domain verification apex ↔ www redirects gu ceart agus tha e nas soilleire mu dè an luach a thèid san field Host aig an TXT-record.

Cruth

Tha tag air gach entry gus an urrainn dhut skim:

• ÙR Check, surface, no feature ùr.
• LEASAICHTE Dh'fhàs existing behaviour nas fheàrr — nas accurate, nas luaithe, nas soilleire.
• CEARTAICHTE Bug a chuir sinn a-mach agus a cheart sinn às dèidh sin.
• TÈARAINTEACHD Hardening, vulnerability fixes, no compliance changes.

Mhothaich thu rud a bhris agus nach eil logged an seo? Cuir email gu support@fixvibe.app.