# CVE-2026-108126: Temporal Proxy encryption key isolation bypass across namespaces

Source: https://junglewise.ai/threats/cve-2026-108126-temporal-proxy-0-2-0-through-0-8-0-does-not-bind-encrypted  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-15. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-108126 · Severity: info · Published 2026-10-15

Temporal Proxy is a middleware that encrypts workflow payloads in the Temporal serverless workflow engine. Versions 0.2.0 through 0.8.0 fail to bind encrypted payloads to the namespace they were encrypted for. An attacker with read access to namespace A and write/read access to namespace B can exploit this to decrypt payloads from namespace A through namespace B, bypassing encryption-based namespace isolation.

Vendors: [Temporal Technologies](https://junglewise.ai/threats/vendors/temporal-technologies).

## Quick answers

**Is CVE-2026-108126 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-108126 being exploited in the wild.

**How severe is CVE-2026-108126?** Informational severity, published 15 October 2026.

**Which products and versions are affected?** Temporal Technologies Temporal Proxy 0.2.0 through 0.8.0.

**Is there a fix for CVE-2026-108126?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-108126 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-108126?** Check whether you run Temporal Technologies Temporal Proxy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability stems from the proxy selecting decryption keys by an identifier stored in the payload rather than validating the namespace context. The ciphertext does not authenticate the namespace, allowing an attacker authorized only for namespace B to decrypt payloads from namespace A if they can obtain the encrypted data. An attacker with dual-namespace write/read access can place a foreign encrypted payload in their writable namespace and retrieve it decrypted through the proxy.

## Affected products

- Temporal Technologies Temporal Proxy 0.2.0 through 0.8.0

## Timeline

- 2026-10-15: disclosed

## References

- [https://pkg.go.dev/](https://pkg.go.dev/)
- [https://github.com/temporalio/temporal-proxy/blob/v0.8.0/pkg/crypto/dek.go](https://github.com/temporalio/temporal-proxy/blob/v0.8.0/pkg/crypto/dek.go)