Skip to main content
CVE-2026-132559VulnerabilityPublished

When payload encryption is enabled, failure messages and stack traces that temporal-proxy is configured to keep from

Affects temporal-proxySource GCVE Database

0
Compare
Authoritative record:CVE-2026-132559· Low 2.3

Not known to be exploited · CVSS 2.3 Low · fixed in 1.0.2 : update temporal-proxy when convenient.

Data as of 18 Nov 2026, 22:49 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Temporal)CVSS 4.02.3
Patch
Available – fixed in 1.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubtemporalio/temporal-proxypkg:github/temporalio/temporal-proxyOther threatsAffected
  • >=0.9.0 <=1.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade temporal-proxy to fixed versions 1.0.2, 1.1.2, or 1.2.1 depending on the deployed minor release line. No other mitigation is indicated.

Description

A vulnerability in temporal-proxy versions 0.9.0 through 1.2.0 allows failure messages and stack traces to be exposed in plaintext when payload encryption is enabled. This occurs because the proxy decrypts failure attributes and forwards the plaintext messages to the upstream Temporal service, which stores them alongside encrypted copies. The issue affects deployments with failure encryption enabled in the proxy or where the SDK encodes failure attributes. Fixed versions are 1.0.2, 1.1.2, and 1.2.1.

References

Community reviews

Loading reviews…