Журнал изменений

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 headers применяются только к root HTML responses. Отсутствие CSP, Permissions-Policy, X-Frame-Options или Referrer-Policy на 204, JSON API, file download или 404 больше не создает finding. 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, рискованные workflow files и outdated dependencies — даже не загружая твой deployed site. См. Типы сканирования.
• НОВОЕSAST checks для рискованного JavaScript. Repo scans теперь flag new Function() и setTimeout("string") — оба эквивалентны eval(), если получают untrusted input.
• ИСПРАВЛЕНОЛожные findings «exposed file» на сайтах Vercel / Cloudflare. Голые responses 403 Forbidden больше не reported as «file exists» — большинство edge providers возвращают 403 для подозрительных paths независимо от того, есть ли там file. Теперь перед 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 больше не reported as JWT-in-storage finding — anon key является публично предназначенным 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 корректно обрабатывает redirects apex ↔ www и яснее объясняет, какое value указывать в поле Host для TXT-record.

Формат

Каждая запись помечена тегом, чтобы ты мог быстро просматривать:

• НОВОЕ Новая проверка, поверхность или функция.
• УЛУЧШЕНО Существующее поведение стало лучше — точнее, быстрее, понятнее.
• ИСПРАВЛЕНО Баг, который мы выпустили, а потом исправили.
• БЕЗОПАСНОСТЬ Усиление защиты, исправления уязвимостей или изменения для compliance.

Заметил, что что-то сломалось и здесь не записано? Напиши на support@fixvibe.app.