CVE-2026-130092: temporal-proxy · Unthrottled Resource Allocation
Affects temporal-proxySource CVE Database V5
Not known to be exploited · CVSS 8.7 High · fixed in 1.2.1 : patch temporal-proxy soon.
Data as of 18 Nov 2026, 20:35 UTC
Thin evidence
One scorer or none| CNA (Temporal) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 1.2.1, 1.1.2, 1.0.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Upgrade temporal-proxy and github.com/temporalio/temporal-proxy to 1.2.1, 1.1.2 or 1.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| temporal-proxygithub.com/temporalio/temporal-proxy | Affected
| Fixed in
|
Gogithub.com/temporalio/temporal-proxypkg:golang/github.com/temporalio/temporal-proxyOther threats | Affected
| 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 one of the fixed versions: 1.0.2, 1.1.2, or 1.2.1. These versions contain the fix that prevents unbounded metric series growth. No other mitigations are indicated. If upgrading is not immediately possible, restrict network access to the gRPC listener to trusted clients only to reduce exposure.
Description
CVE-2026-130092 is a high-severity vulnerability in Temporal Technologies' temporal-proxy component affecting versions from 0.1.0-alpha.20260716 through 1.2.0. An unauthenticated or authenticated caller able to reach the gRPC listener can cause unbounded memory growth by sending requests with many distinct gRPC method names. This happens because temporal-proxy tracks request metrics labeled by method names without limits or removal, leading to resource exhaustion and potential process termination. Fixed versions include 1.0.2, 1.1.2, and 1.2.1.
References
- github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/server/reporter.go (opens in a new tab)
- github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/dataplane/dataplane.go (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/288 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/f745e71918dc386524a606eff1153dbd0f2b0091 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/289 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/87254989bf135dfaf8176e0c822d24aa86907c78 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/290 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/700fc2eae5196ce612eac4b7e8e25877269f6c05 (opens in a new tab)
- github.com/temporalio/temporal-proxy/pull/291 (opens in a new tab)
- github.com/temporalio/temporal-proxy/commit/4b9aba1b14d9b656c32bb3394de7ab820b33c98a (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.0.2 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.1.2 (opens in a new tab)
- github.com/temporalio/temporal-proxy/releases/tag/v1.2.1 (opens in a new tab)