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-2026-130092
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-129186 (ENISA EUVD) · GHSA-8ph7-rpwq-6342 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity87% × 45%Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it. - EPSS PROB
- 0.6%
- EPSS %ILE
- 50th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 18, 2026
Last Modified
November 18, 2026
Advisory Details (10)
Auto-updated Nov 18, 2026commit 4b9aba1b14d9 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit 4b9aba1b14d9 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/4b9aba1b14d9b656c32bb3394de7ab820b33c98a[server]: Bound caller-controlled metric labels (v1.2.x backport)
Fix merged in temporalio/temporal-proxy PR #291 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/291commit 700fc2eae519 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit 700fc2eae519 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/700fc2eae5196ce612eac4b7e8e25877269f6c05[server]: Bound caller-controlled metric labels (v1.1.x backport)
Fix merged in temporalio/temporal-proxy PR #290 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/290commit 87254989bf13 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit 87254989bf13 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/87254989bf135dfaf8176e0c822d24aa86907c78[server]: Bound caller-controlled metric labels (v1.0.x backport)
Fix merged in temporalio/temporal-proxy PR #289 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/289commit f745e71918dc (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit f745e71918dc — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/f745e71918dc386524a606eff1153dbd0f2b0091[server]: Bound caller-controlled metric labels
Fix merged in temporalio/temporal-proxy PR #288 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/288temporal-proxy/internal/dataplane/dataplane.go at v1.2.0 · temporalio/temporal-proxy · GitHub
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/dataplane/dataplane.go#L185-L192temporal-proxy/internal/server/reporter.go at v1.2.0 · temporalio/temporal-proxy · GitHub
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/server/reporter.go#L69-L94Vendor Advisories for CVE-2026-130092(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.6% · 50th percentile
- 2026-11-20 01:27 UTCEchelonGraph re-scored
- 2026-11-20 01:27 UTCGHSA enrichmentGHSA-8ph7-rpwq-6342 · GitHub severity HIGH
- 2026-11-19 20:56 UTCOSV refresh
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
- 2026-11-18 22:28 UTCGHSA enrichmentGHSA-8ph7-rpwq-6342 · GitHub severity HIGH
- 2026-11-18 21:46 UTCGHSA enrichmentGHSA-8ph7-rpwq-6342 · GitHub severity HIGH
- 2026-11-18 21:28 UTCEchelonGraph re-scored
- 2026-11-18 21:03 UTCENISA EUVD ID recordedEUVD-2026-129186 · Source: ENISA EUVD
- 2026-11-18 20:28 UTCEchelonGraph re-scoredFirst assessed: 8.7 HIGH
- 2026-11-18 20:27 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-130092?
When was the CVE record for CVE-2026-130092 published?
Is CVE-2026-130092 actively exploited?
What is the CVSS score of CVE-2026-130092?
How do I remediate CVE-2026-130092?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-130092
Is Your Infrastructure Affected by CVE-2026-130092?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.