CVE-2025-14987

{"id": "CVE-2025-14987", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security@temporal.io", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/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": "LOW", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "LOW", "vulnAvailabilityImpact": "LOW", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "vulnConfidentialityImpact": "LOW", "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"}}]}, "published": "2025-12-30T21:15:43.343", "references": [{"url": "https://github.com/temporalio/temporal/releases/tag/v1.27.4", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/temporal/releases/tag/v1.28.2", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/temporal/releases/tag/v1.29.2", "source": "security@temporal.io"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@temporal.io", "description": [{"lang": "en", "value": "CWE-863"}]}], "descriptions": [{"lang": "en", "value": "When system.enableCrossNamespaceCommands is enabled (on by default), the Temporal server permits certain workflow task commands (e.g. StartChildWorkflowExecution, SignalExternalWorkflowExecution, RequestCancelExternalWorkflowExecution) to target a different namespace than the namespace authorized at the gRPC boundary. The frontend authorizes RespondWorkflowTaskCompleted based on the outer request namespace, but the history service later resolves and executes the command using the namespace embedded in command attributes without authorizing the caller for that target namespace. This can allow a worker authorized for one namespace to create, signal, or cancel workflows in another namespace.\nThis issue affects Temporal: through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2."}, {"lang": "es", "value": "Cuando system.enableCrossNamespaceCommands est\u00e1 habilitado (activado por defecto), el servidor Temporal permite que ciertos comandos de tareas de flujo de trabajo (p. ej., StartChildWorkflowExecution, SignalExternalWorkflowExecution, RequestCancelExternalWorkflowExecution) apunten a un espacio de nombres diferente al espacio de nombres autorizado en el l\u00edmite gRPC. El frontend autoriza RespondWorkflowTaskCompleted bas\u00e1ndose en el espacio de nombres de la solicitud externa, pero el servicio de historial posteriormente resuelve y ejecuta el comando utilizando el espacio de nombres incrustado en los atributos del comando sin autorizar al llamador para ese espacio de nombres de destino. Esto puede permitir que un trabajador autorizado para un espacio de nombres cree, se\u00f1ale o cancele flujos de trabajo en otro espacio de nombres.\nEste problema afecta a Temporal: hasta 1.29.1. Corregido en 1.27.4, 1.28.2, 1.29.2."}], "lastModified": "2026-04-15T00:35:42.020", "sourceIdentifier": "security@temporal.io"}