Registro de cambios

May 18, 2026

• NUEVOelecterm 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.
• NUEVOOpenCms 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

• NUEVOFUXA 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.
• NUEVOCKAN 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

• NUEVOPDF.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.
• NUEVOActive 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.
• NUEVOSafer 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.
• NUEVOFirst-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.
• MEJORADOImproved 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.
• MEJORADOImproved 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.
• MEJORADOImproved 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.
• MEJORADOCSP header evidence and fix prompts improved. Missing-CSP reports now include clearer hosting and response context plus safer framework-aware remediation guidance.
• CORREGIDOVercel 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.
• CORREGIDOLos hallazgos de cumplimiento ya no llevan etiquetas CWE engañosas. El check legal-compliance antes etiquetaba los hallazgos de "falta política de privacidad" y "faltan términos" con CWE-359 (exposición de PII), que no describe la brecha real. Ahora se publican sin CWE — son items de cumplimiento, no debilidades de seguridad clasificables.

May 15, 2026

• NUEVOAdditional research-informed checks. FixVibe shipped more coverage based on recent vulnerability research and mapped duplicate topics to existing scanner modules where coverage already existed.
• NUEVOVerificación de fuga de secretos en el repositorio. Las exploraciones de repositorios de GitHub ahora pueden marcar claves de proveedor codificadas de forma fija y valores de alta entropía similares a secretos enviados al código, con la evidencia enmascarada y el aviso de rotación estándar de FixVibe incluido.
• NUEVOVercel 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

• NUEVOLiteLLM 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.
• NUEVOLibreNMS 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.
• MEJORADOFirebase 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

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

• NUEVORepo 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.
• NUEVONext.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 mayo de 2026

• SEGURIDADCross-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.
• CORREGIDOSupabase 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.
• MEJORADOLos hallazgos de headers de seguridad solo aplican a respuestas HTML raíz. La falta de CSP, Permissions-Policy, X-Frame-Options o Referrer-Policy en un 204, una API JSON, una descarga de archivo o un 404 ya no produce un hallazgo. HSTS y X-Content-Type-Options todavía se evalúan en todas las respuestas.
• MEJORADOAuth-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.
• MEJORADOFile-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 mayo de 2026

• CORREGIDOThreat-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.
• NUEVOEscaneos de repositorios de GitHub. Conecta un repo y FixVibe revisa el código fuente en busca de service keys de Supabase filtradas, tokens admin de Firebase, archivos de workflow riesgosos y dependencias desactualizadas, sin cargar nunca tu sitio desplegado. Consulta Tipos de escaneo.
• NUEVOComprobaciones SAST para JavaScript riesgoso. Los escaneos de repositorio ahora marcan new Function() y setTimeout("string"); ambos equivalen a eval() cuando reciben entrada no confiable.
• CORREGIDOFalsos hallazgos de “archivo expuesto” en sitios de Vercel / Cloudflare. Las respuestas 403 Forbidden sin más ya no se reportan como “el archivo existe”; la mayoría de proveedores edge devuelve 403 para rutas con aspecto sospechoso tanto si el archivo está como si no. Ahora exigimos una señal HTTP positiva antes de marcar.
• CORREGIDORepo-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.
• CORREGIDOUna anon key de Supabase en localStorage ya no se reporta como hallazgo de JWT en almacenamiento: la anon key es el token de cliente destinado a ser público. Los tokens service-role reales en almacenamiento del navegador ahora son critical con un título más claro.
• CORREGIDOCSP weakness detection improved. Content-Security-Policy checks now catch more permissive source policies while keeping evidence and remediation focused on the effective browser policy.
• CORREGIDOReflected-XSS check tightened. Active scans now require stronger reflection evidence before reporting executable-context risk, reducing false positives from unrelated markup on the page.
• CORREGIDOLa verificación de dominio maneja correctamente redirects apex ↔ www y es más clara sobre qué valor va en el campo Host del registro TXT.

Formato

Cada entrada está etiquetada para que puedas escanear rápido:

• NUEVO Una comprobación, superficie o función nueva.
• MEJORADO El comportamiento existente mejoró: más preciso, más rápido o más claro.
• CORREGIDO Un bug que lanzamos y luego corregimos.
• SEGURIDAD Endurecimiento, correcciones de vulnerabilidades o cambios de cumplimiento.

¿Ves algo que se rompió y no está registrado aquí? Escribe a support@fixvibe.app.