CVE-2026-67531

{"id": "CVE-2026-67531", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-67531", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-06T18:38:14.596272Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "agentfront", "product": "frontmcp", "versions": [{"status": "affected", "version": "< 1.5.7"}]}]}], "published": "2026-08-06T00:16:53.733", "references": [{"url": "https://github.com/agentfront/frontmcp/commit/209cddd19a8d4db0777f725b527818da7df6f67f", "source": "security-advisories@github.com"}, {"url": "https://github.com/agentfront/frontmcp/security/advisories/GHSA-mp29-fxh8-92px", "source": "security-advisories@github.com"}, {"url": "https://github.com/agentfront/frontmcp/security/advisories/GHSA-mp29-fxh8-92px", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-94"}]}], "descriptions": [{"lang": "en", "value": "FrontMCP is a TypeScript-first framework for the Model Context Protocol (MCP). Prior to 1.5.7, the sandboxed codecall:execute\u00a0tool exposes live host Zod\u00a0schema instances to the script via\u00a0getTool(), and because Zod v4 defines\u00a0_zod as a non-configurable, non-writable own property, the ECMAScript Proxy invariants force the security membrane to hand back the raw host object, letting a script reach\u00a0_zod.constr.constructor\u00a0(the host Function\u00a0constructor) and execute arbitrary code in the server process. A single tools/call is sufficient to escape the sandbox and achieve remote code execution as the server user, exposing everything the process holds such as OAuth client secrets, JWT_SECRET, session keys, database credentials, and cloud instance metadata. Because the framework's\u00a0DEFAULT_AUTH_OPTIONS\u00a0is public mode, an unconfigured server serves this to unauthenticated callers, and on authenticated servers an indirect prompt injection in tool output or fetched content can trigger it without a human attackerThis issue is fixed in version 1.5.7."}, {"lang": "es", "value": "FrontMCP es un framework TypeScript-first para el Protocolo de Contexto de Modelo (MCP). Antes de la versi\u00f3n 1.5.7, la herramienta sandboxed codecall:execute expone instancias de esquema Zod de host en vivo al script a trav\u00e9s de getTool(), y debido a que Zod v4 define _zod como una propiedad propia no configurable y no escribible, los invariantes del Proxy de ECMAScript fuerzan a la membrana de seguridad a devolver el objeto host sin procesar, permitiendo que un script alcance _zod.constr.constructor (el constructor de la Funci\u00f3n del host) y ejecute c\u00f3digo arbitrario en el proceso del servidor. Una sola llamada a tools/call es suficiente para escapar del sandbox y lograr la ejecuci\u00f3n remota de c\u00f3digo como el usuario del servidor, exponiendo todo lo que el proceso contiene, como secretos de cliente de OAuth, JWT_SECRET, claves de sesi\u00f3n, credenciales de base de datos y metadatos de instancia en la nube. Debido a que DEFAULT_AUTH_OPTIONS del framework est\u00e1 en modo p\u00fablico, un servidor no configurado sirve esto a los llamantes no autenticados, y en servidores autenticados una inyecci\u00f3n de prompt indirecta en la salida de la herramienta o en el contenido recuperado puede activarlo sin un atacante humano. Este problema est\u00e1 solucionado en la versi\u00f3n 1.5.7."}], "lastModified": "2026-10-24T16:10:00.153", "sourceIdentifier": "security-advisories@github.com"}