Metrics
Affected Vendors & Products
No advisories yet.
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.
Workaround
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.
Wed, 18 Nov 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Unauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics | |
| Weaknesses | CWE-770 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Temporal
Published:
Updated: 2026-11-18T20:18:59.367Z
Reserved: 2026-11-16T21:00:01.805Z
Link: CVE-2026-130092
No data.
No data.
No data.
OpenCVE Enrichment
No data.