CVE-2026-130092: Unauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
temporal-proxyto a version that resolves this vulnerability.Fixed in 1.0.2 - Upgrade
Upgrade
temporal-proxyto a version that resolves this vulnerability.Fixed in 1.1.2 - Upgrade
Upgrade
temporal-proxyto a version that resolves this vulnerability.Fixed in 1.2.1
Event History
Frequently Asked Questions
Who can trigger the memory growth?
Any caller that can reach the temporal-proxy gRPC listener can trigger it, including unauthenticated callers. Valid credentials are not required because requests are recorded even when authentication or routing rejects them.
Does disabling or not scraping the metrics endpoint prevent exploitation?
No. Metric series are created and retained regardless of whether the metrics endpoint is scraped.
Which deployments are affected and how should they be remediated?
Versions from 0.1.0-alpha.20260716 through 1.2.0 are affected. Upgrade within the deployed release line to 1.0.2, 1.1.2, or 1.2.1; releases before 1.0.0 do not receive a fix.
What conditions increase the rate of memory growth?
Sending requests with many distinct gRPC method names creates additional retained metric series. Configuring metric labels from request metadata multiplies that growth.