CVE-2026-130092
High 8.7No known exploitationFix availableUnauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 51% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
A caller who can reach the temporal-proxy gRPC listener, with or without a valid credential, can grow the proxy's memory until the process is terminated by sending requests with many distinct gRPC method names. temporal-proxy labels its request metrics with the method name exactly as the caller sent it, and records every request, including those that authentication or routing reject. Each distinct method name adds metric series that are never removed. The series grow whether or not the metrics endpoint is scraped, and metric labels configured from request metadata multiply the growth. temporal-proxy versions 0.1.0-alpha.20260716 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.
Weakness: CWE-770
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Temporal))
- Fix documented (source date)
- Vendor solution
- Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases report any method outside the services the proxy forwards as unknown and limit each metadata label to 100 distinct values. Releases before 1.0.0 receive no fix.
- Mitigation
- Restrict network access to the proxy's gRPC listener to trusted clients, or place the proxy behind a gateway that forwards only known Temporal service method paths.
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Temporal Technologies, Inc. | temporal-proxy | from 0.1.0-alpha.20260716 up to and including 0.10.1 | Not documented | CVE Program |
| Temporal Technologies, Inc. | temporal-proxy | from 1.0.0 before 1.0.2 | 1.0.2 | CVE Program |
| Temporal Technologies, Inc. | temporal-proxy | from 1.1.0 before 1.1.2 | 1.1.2 | CVE Program |
| Temporal Technologies, Inc. | temporal-proxy | from 1.2.0 before 1.2.1 | 1.2.1 | CVE Program |
Timeline
Disclosure
CVE record published by Temporal
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Temporal)
Vendor guidance and references
- Backport commit on releases/v1.2.x (opens in a new tab)patch
- Backport commit on releases/v1.1.x (opens in a new tab)patch
- Backport commit on releases/v1.0.x (opens in a new tab)patch
- Fix commit (opens in a new tab)patch
- Fix pull request (opens in a new tab)patch
- Backport pull request for the 1.0 release line (opens in a new tab)patch
- Backport pull request for the 1.1 release line (opens in a new tab)patch
- Backport pull request for the 1.2 release line (opens in a new tab)patch
- temporal-proxy 1.0.2 (opens in a new tab)release-notes
- temporal-proxy 1.1.2 (opens in a new tab)release-notes
- temporal-proxy 1.2.1 (opens in a new tab)release-notes
- Interceptor order in temporal-proxy 1.2.0, with the reporter ahead of authentication (opens in a new tab)product
- Request metric reporter in temporal-proxy 1.2.0, labeled by the caller-supplied method name (opens in a new tab)product