CVE-2026-108126

temporal-proxy payload decryption is not bound to the request namespace

  • Medium 6.0

Description

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.

Key facts

Published
15 Oct 2026
Last changed
16 Oct 2026
Assigned by
Temporal
EPSS
0.356% likely to be exploited in the next 30 days, higher than 29.865% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.0CVSS 4.0, Mediumfrom the CNA (Temporal)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

What to do

  • Upgrade to temporal-proxy 0.9.0 or later and set encryption.namespaceBinding to strict. Fixed releases record the namespace in each payload they encrypt and, in strict mode, refuse to decrypt a payload recorded for another namespace or for none, including through the codec server's /decode endpoint, which then requires the caller to name a namespace. The setting has no default and must be set whenever encryption keys are configured. The off and permissive modes exist to migrate payloads encrypted by earlier releases, which carry no namespace, and do not close this issue; move to strict once the vault_unbound_opens_total and vault_namespace_mismatches_total metrics have stayed at zero for longer than namespace retention. Payloads carried in Nexus operations are not compared, because they cross namespaces by design.CNA solution statement
  • Until a fixed release is deployed, serve namespaces that must stay isolated from each other through separate proxy deployments, or use KMS key policies that let each proxy use only the keys of the namespaces it serves. Giving each namespace its own key on a single proxy does not help, because that proxy holds all of them. Leaving the codec server disabled closes the /decode route only.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

Disclosure, across the namespace authorization boundary, of payloads the proxy encrypted: Workflow and Activity inputs and results, and Signal and Update arguments. Encrypted payloads cannot be modified through this issue, and data the proxy does not encrypt is not affected. No availability impact was identified. (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Temporal Technologies, Inc.temporal-proxy
  • Default status: unaffected
  • 0.2.0 up to but excluding 0.9.0 (affected)

Timeline

  1. 15 Oct 2026 Published

Weakness

References