CVE Catalog

CVE-2026-108126

MediumCVSS 6.0
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.36%

28th percentile - higher than 28% of all known CVEs

Summary

temporal-proxy versions 0.2.0 through 0.8.0 does not bind encrypted payloads to the namespace they were encrypted for. The proxy selects the decryption key based on an identifier in the payload rather than the request namespace, allowing an attacker authorized for namespace B to decrypt a payload from namespace A.

Risk Assessment

An attacker with limited privileges could access encrypted data from another namespace, breaking isolation and potentially leading to information disclosure.

Recommendation

Update temporal-proxy to a version newer than 0.8.0 that binds payloads to namespaces, and restrict write permissions to namespaces.

Related vulnerabilities

Original NVD description (English source)

temporal-proxy 0.2.0 through 0.8.0 does not bind encrypted payloads to the namespace they were encrypted for. When payload encryption is enabled, the proxy chooses the decryption key by an identifier stored in the payload rather than by the namespace of the request, and nothing in the ciphertext records that namespace. A caller whom the proxy authorizes only for namespace B, and who has obtained an encrypted payload from namespace A, can therefore have the proxy decrypt it. In 0.8.0, the caller can submit the payload to the codec server's /decode endpoint. In every affected version, a caller who can also write to namespace B on the Temporal server directly can place the payload there and read it back through the proxy. This holds whether namespaces share the default key or each has its own, because a single proxy holds every key it is configured with. The issue does not give the attacker encrypted payloads they could not already obtain, and does not allow encrypted payloads to be modified.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS