Answer in brief
CVE-2026-130092 records a High severity (CVSS 8.7) vulnerability in Unauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics. The current sources do not mark it as known exploited. The current feed maps Temporal Technologies, Inc./github.com/temporalio/temporal-proxy (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Temporal Technologies, Inc./github.com/temporalio/temporal-proxy (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Temporal Technologies, Inc./github.com/temporalio/temporal-proxygeneric | >=0.1.0-alpha.20260716 <=0.10.1 || >=1.0.0 <1.0.2 || >=1.1.0 <1.1.2 || >=1.2.0 <1.2.1 | 1.0.2, 1.1.2, 1.2.1 |
Published upstream
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.