Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Temporal

  2. · 6 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-108126, by who scored it
Scored byCVSSScoreVector
TemporalCNA (assigner)4.0Medium6.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
NVDNVD · Awaiting Analysis4.0Medium6.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/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
EPSS (exploitation in 30 days)
0.36% · top 70% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.0.

Affected products

What to do

Solution: 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.

Workaround: 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.

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-108126 badge
[![CVE-2026-108126](https://cveledger.app/badge/CVE-2026-108126.svg)](https://cveledger.app/cve/CVE-2026-108126)

Record last updated .