CVE
Temporal Technologies temporal-proxy denial of service in gRPC metrics
Affects temporal-proxy 0.1.0-alpha.20260716 through 0.10.1 and 1.0.0 through 1.2.0 before their fixes, where callers can reach the gRPC listener. Fixed in 1.0.2, 1.1.2, and 1.2.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.2, 1.1.2, 1.2.1
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
Temporal-proxy, a product from Temporal Technologies, Inc., can be driven to exhaust its memory and crash. A caller who can reach its gRPC listener, with or without valid credentials, can send requests with many distinct gRPC method names, and the proxy keeps a metric series for each one, so memory grows until the process is terminated.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure25/25Default setups, CISA rates it automatable
- Reach10/20Affects Go packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 1.0.2, 1.1.2, 1.2.1.
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.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130092 (Unauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130092 (entry last updated 2026-11-18):
Affected:
- Go package github.com/temporalio/temporal-proxy: from 0.1.0-alpha.20260716, through 0.10.1; from 1.0.0, fixed in 1.0.2; from 1.1.0, fixed in 1.1.2; from 1.2.0, fixed in 1.2.1
Fixed versions: 1.0.2, 1.1.2, 1.2.1.
Conditions (all must be true for the bug to be hit):
- The caller can reach the proxy's gRPC listener (source: https://www.cve.org/CVERecord?id=CVE-2026-130092)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
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. (source: https://www.cve.org/CVERecord?id=CVE-2026-130092)
CISA KEV: CVE-2026-130092 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130092 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/temporalio/temporal-proxy/pull/288
- https://github.com/temporalio/temporal-proxy/commit/f745e71918dc386524a606eff1153dbd0f2b0091
- https://github.com/temporalio/temporal-proxy/pull/289
- https://github.com/temporalio/temporal-proxy/commit/87254989bf135dfaf8176e0c822d24aa86907c78
- https://github.com/temporalio/temporal-proxy/pull/290
- https://github.com/temporalio/temporal-proxy/commit/700fc2eae5196ce612eac4b7e8e25877269f6c05
- https://github.com/temporalio/temporal-proxy/pull/291
- https://github.com/temporalio/temporal-proxy/commit/4b9aba1b14d9b656c32bb3394de7ab820b33c98a
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130092
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130092"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
From 0.1.0-alpha.20260716 · through 0.10.1; From 1.0.0 · fixed in 1.0.2; From 1.1.0 · fixed in 1.1.2; From 1.2.0 · fixed in 1.2.1
Evidence 15
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130092
Is CVE-2026-130092 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Unauthenticated callers can make temporal-proxy keep adding request metrics without any limit, so its memory use can grow until it is exhausted.Source: cve.org
Which versions are affected by CVE-2026-130092?
github.com/temporalio/temporal-proxy (Go): from 0.1.0-alpha.20260716 through 0.10.1; from 1.0.0 before 1.0.2; from 1.1.0 before 1.1.2; from 1.2.0 before 1.2.1.Source: cve.now feed data
Am I affected, and how do I check?
The affected ranges are 0.1.0-alpha.20260716 through 0.10.1, and 1.0.0 before 1.0.2, 1.1.0 before 1.1.2, and 1.2.0 before 1.2.1. The advisory says every deployment whose gRPC listener the caller can reach is affected, so compare the deployed temporal-proxy version with these ranges and check who can reach the gRPC listener.Source: cve.org
How do I fix CVE-2026-130092?
Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line.Source: cve.org