Журнал змін

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.
• ВИПРАВЛЕНОЗнахідки відповідності більше не несуть оманливих CWE-міток. Раніше перевірка legal-compliance позначала «відсутня політика конфіденційності» та «відсутні умови» міткою CWE-359 (розкриття PII), що не описує реальний пробіл. Тепер ці знахідки публікуються без CWE — це питання відповідності, а не класифіковані вразливості.

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.
• НОВЕПеревірка витоку секретів у репозиторії. Сканування репозиторіїв GitHub тепер може позначати жорстко закодовані ключі постачальників і значення з високою ентропією, схожі на секрети, які потрапили в код — з замаскованими доказами та стандартною підказкою ротації FixVibe.
• НОВЕ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 більше не створюють знахідку. HSTS і X-Content-Type-Options усе ще оцінюються по всіх 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. Див. Типи сканувань.
• НОВЕSAST checks for risky JavaScript. Repo scans тепер flag new Function() і setTimeout("string") — обидва equivalent to eval(), коли отримують untrusted input.
• ВИПРАВЛЕНОFalse “exposed file” findings на Vercel / Cloudflare sites. Bare 403 Forbidden responses більше не reported as “file exists” — більшість edge providers повертають 403 для suspicious-looking paths незалежно від того, чи файл існує. Тепер перед flagging ми вимагаємо positive HTTP signal.
• ВИПРАВЛЕНО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 більше не reports as JWT-in-storage finding — anon key є публічно призначеним client token. Справжні service-role tokens у browser storage тепер critical з яснішою назвою.
• ВИПРАВЛЕНО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 коректно обробляє redirects apex ↔ www і ясніше пояснює, яке значення йде в поле Host TXT-record.

Формат

Кожен запис має тег, щоб ти міг швидко переглянути:

• НОВЕ Нова перевірка, поверхня або функція.
• ПОКРАЩЕНО Наявна поведінка стала кращою — точнішою, швидшою, зрозумілішою.
• ВИПРАВЛЕНО Помилка, яку ми випустили, а потім виправили.
• БЕЗПЕКА Укріплення, виправлення вразливостей або зміни для compliance.

Помітив щось, що зламалося й не записано тут? Напиши на support@fixvibe.app.