ענדערונגס־לאָג

May 18, 2026

• נײַelecterm 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.
• נײַOpenCms 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

• נײַFUXA 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.
• נײַCKAN 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

• נײַPDF.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.
• נײַActive 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.
• נײַSafer 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.
• נײַFirst-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.
• פֿאַרבעסערטImproved 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.
• פֿאַרבעסערטImproved 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.
• פֿאַרבעסערטImproved 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.
• פֿאַרבעסערטCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• פֿאַרראָכטןVercel 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.
• פֿאַרראָכטןCompliance 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

• נײַAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• נײַRepository 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.
• נײַVercel 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

• נײַLiteLLM 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.
• נײַLibreNMS 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.
• פֿאַרבעסערטFirebase 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

• נײַRepo 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.
• נײַSupabase Storage posture check. Passive scans can now review public Supabase Storage buckets and anonymous object-listing exposure alongside existing RLS and key checks.
• נײַAI-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

• נײַRepo 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.
• נײַNext.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טן מײַ 2026

• זיכערהייטCross-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.
• פֿאַרראָכטןSupabase 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.
• פֿאַרבעסערטSecurity-header findings גילטן נאָר אויף root HTML responses. Missing CSP, Permissions-Policy, X-Frame-Options, אָדער Referrer-Policy אויף אַ 204, JSON API, file download, אָדער 404 מאַכט מער נישט קיין finding. HSTS און X-Content-Type-Options gradeן נאָך אַלע responses.
• פֿאַרבעסערטAuth-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.
• פֿאַרבעסערטFile-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טן מײַ 2026

• פֿאַרראָכטןThreat-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.
• נײַGitHub repo scans. פֿאַרבינד אַ repo און FixVibe קאָנטראָלירט דעם source פֿאַר leaked Supabase service keys, Firebase admin tokens, risky workflow files, און outdated dependencies — אָן קיינמאָל לאָדן דײַן deployed site. זע Scan טיפּן.
• נײַSAST checks פֿאַר risky JavaScript. Repo scans flagן איצט new Function() און setTimeout("string") — ביידע equivalent צו eval() ווען מען גיט זיי untrusted input.
• פֿאַרראָכטןפֿאַלשע “exposed file” findings אויף Vercel / Cloudflare sites. Bare 403 Forbidden responses ווערן מער נישט reported ווי “file exists” — רובֿ edge providers געבן 403 פֿאַר suspicious-looking paths צי דער file איז דאָרט צי נישט. מיר דאַרפֿן איצט אַ positive HTTP signal איידער flagging.
• פֿאַרראָכטןRepo-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.
• פֿאַרראָכטןSupabase anon key אין localStorage ווערט מער נישט reported ווי אַ JWT-in-storage finding — דער anon key איז דער publicly-intended client token. אמתע service-role tokens אין browser storage זענען איצט critical מיט אַ קלאָרערן title.
• פֿאַרראָכטןCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• פֿאַרראָכטןReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• פֿאַרראָכטןDomain verification באַהאַנדלט apex ↔ www redirects ריכטיק און איז קלאָרער וועגן וועלכן value גייט אין דעם TXT-record Host field.

פֿאָרמאַט

יעדער entry איז tagged אַזוי דו קענסט שנעל איבערקוקן:

• נײַ אַ נײַער check, surface, אָדער feature.
• פֿאַרבעסערט עקזיסטירנדיקער behaviour איז געוואָרן בעסער — מער accurate, faster, clearer.
• פֿאַרראָכטן אַ bug וואָס מיר האָבן shipped און דערנאָך squashed.
• זיכערהייט Hardening, vulnerability fixes, אָדער compliance changes.

געזען עפּעס וואָס איז צעבראָכן און נישט logged דאָ? Email support@fixvibe.app.