Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
Temporal Technologies, Inc. temporal-proxy
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 temporal-proxy 0.2.0 至 0.8.0 版本中，加密负载（encrypted payloads）未与其加密时所归属的命名空间（namespace）进行绑定。当启用负载加密功能时，代理（proxy）依据负载中存储的标识符来选择解密密钥，而非根据请求所属的命名空间进行选择，且密文本身并不记录该命名空间信息。因此，若一个被代理仅授权访问命名空间 B 的调用者，从命名空间 A 获取了一个加密负载，则该调用者可要求代理对该负载进行解密。在 0.8.0 版本中，该调用者可将此负载提交至编解码器服务器（co

CVSS 6.0 · Medium EPSS 0.36% · P28

Affected Version Matrix 1

VendorProduct Version RangeStatus
Temporal Technologies, Inc. temporal-proxy 0.2.0< 0.9.0 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-108126

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
temporal-proxy payload decryption is not bound to the request namespace
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Temporal Technologies, Inc. temporal-proxy 0.2.0 ~ 0.9.0 -

II. Public POCs for CVE-2026-108126

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-108126

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-108126 (4)

News Coverage for CVE-2026-108126 (1)

IV. Related Vulnerabilities

Same vendor: Temporal Technologies, Inc.
Same weakness: CWE-639

V. Comments for CVE-2026-108126

No comments yet

Leave a comment