Cofnod newidiadau

May 18, 2026

• NEWYDDelecterm 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.
• NEWYDDOpenCms 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

• NEWYDDFUXA 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.
• NEWYDDCKAN 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

• NEWYDDPDF.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.
• NEWYDDActive 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.
• NEWYDDSafer 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.
• NEWYDDFirst-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.
• GWELLImproved 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.
• GWELLImproved 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.
• GWELLImproved 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.
• GWELLCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• WEDI TRWSIOVercel 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.
• WEDI TRWSIOCompliance 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

• NEWYDDAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NEWYDDGwiriad gollyngiad cyfrinach storfa. Gall sganiau storfa GitHub bellach faner allweddau darparwr wedi'u codio'n galed a gwerthoedd entropi uchel tebyg i gyfrinachau a ymrwymwyd i'r ffynhonnell, gyda thystiolaeth wedi'i guddio a phrydlon cylchdroi safonol FixVibe wedi'i gynnwys.
• NEWYDDVercel 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

• NEWYDDLiteLLM 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.
• NEWYDDLibreNMS 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.
• GWELLFirebase 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

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

• NEWYDDRepo 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.
• NEWYDDNext.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 Mai 2026

• DIOGELWCHCross-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.
• WEDI TRWSIOSupabase 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.
• GWELLMae canfyddiadau security-header yn berthnasol i ymatebion root HTML yn unig. Nid yw CSP, Permissions-Policy, X-Frame-Options, neu Referrer-Policy coll ar 204, JSON API, file download, neu 404 bellach yn cynhyrchu canfyddiad. Mae HSTS a X-Content-Type-Options yn dal i raddio ar draws pob ymateb.
• GWELLAuth-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.
• GWELLFile-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 Mai 2026

• WEDI TRWSIOThreat-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.
• NEWYDDSganiau repo GitHub. Cysylltwch repo ac mae FixVibe yn gwirio'r ffynhonnell am leaked Supabase service keys, Firebase admin tokens, risky workflow files, ac outdated dependencies, heb lwytho eich safle deployed byth. Gweler Mathau o sgan.
• NEWYDDChecks SAST ar gyfer JavaScript peryglus. Mae sganiau repo bellach yn flagio new Function() a setTimeout("string"): mae'r ddau'n gyfwerth â eval() pan gânt eu bwydo â mewnbwn annibynadwy.
• WEDI TRWSIOCanfyddiadau “exposed file” ffug ar safleoedd Vercel / Cloudflare. Nid yw ymatebion noeth 403 Forbidden bellach yn cael eu hadrodd fel “file exists”: mae'r rhan fwyaf o edge providers yn dychwelyd 403 ar gyfer paths sy'n edrych yn amheus boed y ffeil yno ai peidio. Rydym bellach yn mynnu signal HTTP cadarnhaol cyn flagio.
• WEDI TRWSIORepo-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.
• WEDI TRWSIONid yw Supabase anon key yn localStorage bellach yn cael ei adrodd fel canfyddiad JWT-in-storage: yr anon key yw'r token cleient sydd wedi'i fwriadu'n gyhoeddus. Mae service-role tokens go iawn yn storfa'r porwr bellach yn critical gyda theitl cliriach.
• WEDI TRWSIOCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• WEDI TRWSIOReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• WEDI TRWSIOMae gwirio parth yn trin redirects apex ↔ www yn gywir ac yn fwy clir ynghylch pa werth sy'n mynd ym maes Host y TXT-record.

Fformat

Mae pob cofnod wedi'i dagio fel y gallwch sgimio:

• NEWYDD Check, arwyneb, neu nodwedd newydd.
• GWELL Ymddygiad presennol wedi gwella: mwy cywir, cyflymach, cliriach.
• WEDI TRWSIO Byg a gludwyd gennym ac wedyn ei wasgu.
• DIOGELWCH Caledu, trwsio gwendidau, neu newidiadau compliance.

Wedi gweld rhywbeth a dorrodd ac nad yw wedi'i gofnodi yma? E-bostiwch support@fixvibe.app.