Registro de alterações

May 18, 2026

• NOVOelecterm 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.
• NOVOOpenCms 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

• NOVOFUXA 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.
• NOVOCKAN 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

• NOVOPDF.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.
• NOVOActive 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.
• NOVOSafer 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.
• NOVOFirst-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.
• MELHORADOImproved 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.
• MELHORADOImproved 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.
• MELHORADOImproved 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.
• MELHORADOCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• CORRIGIDOVercel 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.
• CORRIGIDOOs achados de conformidade não levam mais etiquetas CWE enganosas. O check legal-compliance marcava "política de privacidade ausente" e "termos ausentes" com CWE-359 (exposição de PII), o que não descreve a lacuna real. Esses achados agora saem sem CWE — são itens de conformidade, não fraquezas de segurança classificáveis.

May 15, 2026

• NOVOAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NOVOVerificação de vazamento de segredos no repositório. As varreduras de repositórios do GitHub agora podem sinalizar chaves de provedor hardcoded e valores de alta entropia semelhantes a segredos enviados ao código, com as evidências mascaradas e o prompt de rotação padrão da FixVibe incluído.
• NOVOVercel 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

• NOVOLiteLLM 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.
• NOVOLibreNMS 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.
• MELHORADOFirebase 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

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

• NOVORepo 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.
• NOVONext.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 de maio de 2026

• SEGURANÇACross-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.
• CORRIGIDOSupabase 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.
• MELHORADOFindings de headers de segurança só se aplicam a respostas HTML raiz. CSP, Permissions-Policy, X-Frame-Options ou Referrer-Policy ausentes em 204, API JSON, download de arquivo ou 404 não geram mais finding. HSTS e X-Content-Type-Options continuam avaliados em todas as respostas.
• MELHORADOAuth-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.
• MELHORADOFile-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 de maio de 2026

• CORRIGIDOThreat-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.
• NOVOVarreduras de repositório GitHub. Conecte um repo e o FixVibe verifica o código-fonte em busca de chaves de serviço Supabase vazadas, tokens admin Firebase, arquivos de workflow arriscados e dependências desatualizadas — sem nunca carregar seu site implantado. Veja Tipos de varredura.
• NOVOChecks SAST para JavaScript arriscado. Varreduras de repo agora sinalizam new Function() e setTimeout("string") — ambos equivalentes a eval() quando alimentados com entrada não confiável.
• CORRIGIDOFalsos findings de “arquivo exposto” em sites Vercel / Cloudflare. Respostas 403 Forbidden simples não são mais reportadas como “arquivo existe” — a maioria dos provedores de borda retorna 403 para caminhos com aparência suspeita, exista ou não o arquivo. Agora exigimos um sinal HTTP positivo antes de sinalizar.
• CORRIGIDORepo-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.
• CORRIGIDOChave anon do Supabase em localStorage não é mais reportada como finding de JWT em storage — a chave anon é o token cliente intencionalmente público. Tokens service-role reais em armazenamento do navegador agora são critical com título mais claro.
• CORRIGIDOCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• CORRIGIDOReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• CORRIGIDOA verificação de domínio lida corretamente com redirects apex ↔ www e deixa mais claro qual valor entra no campo Host do registro TXT.

Formato

Cada entrada recebe uma tag para você poder passar os olhos:

• NOVO Um novo check, superfície ou recurso.
• MELHORADO Comportamento existente ficou melhor — mais preciso, mais rápido, mais claro.
• CORRIGIDO Um bug que enviamos e depois corrigimos.
• SEGURANÇA Reforço, correções de vulnerabilidade ou mudanças de conformidade.

Viu algo que quebrou e não está registrado aqui? Envie e-mail para support@fixvibe.app.