A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 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, and rotate any upstream API key that untrusted callers could reach.
CVE-2026-130089
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-129187 (ENISA EUVD) · GHSA-2jp8-mqrx-3pcm (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS
- 7.3
- EG Score
- 7.3HIGHmedium confidence
- EG Risk
- 33EG Risk 33/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)Severity73% × 45%Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 28th
- 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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.3% 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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 every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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, 20261.0.2 Release
Patch available: temporalio/temporal-proxy v1.0.2
https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2commit c73636037045 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit c73636037045 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a[proxy]: Require plain hosts in templated upstream targets (#284)
Fix merged in temporalio/temporal-proxy PR #292 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/292commit dfb4b83f0ed2 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit dfb4b83f0ed2 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90[proxy]: Require plain hosts in templated upstream targets (#284)
Fix merged in temporalio/temporal-proxy PR #293 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/293commit cd60785edd81 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit cd60785edd81 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061[proxy]: Require plain hosts in templated upstream targets (#284)
Fix merged in temporalio/temporal-proxy PR #294 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/294commit b902dcfcc1d3 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit b902dcfcc1d3 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8[proxy]: Require plain hosts in templated upstream targets
Fix merged in temporalio/temporal-proxy PR #284 on 2026-11-17 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/284temporal-proxy/internal/proxy/resolver.go at v1.2.0 · temporalio/temporal-proxy · GitHub
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282Vendor Advisories for CVE-2026-130089(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.3% · 28th percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-20 01:27 UTCEchelonGraph re-scored
- 2026-11-20 01:27 UTCGHSA enrichmentGHSA-2jp8-mqrx-3pcm · GitHub severity HIGH
- 2026-11-19 20:56 UTCOSV refresh
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
- 2026-11-18 22:28 UTCGHSA enrichmentGHSA-2jp8-mqrx-3pcm · GitHub severity HIGH
- 2026-11-18 21:46 UTCGHSA enrichmentGHSA-2jp8-mqrx-3pcm · GitHub severity HIGH
- 2026-11-18 21:28 UTCEchelonGraph re-scored
- 2026-11-18 21:03 UTCENISA EUVD ID recordedEUVD-2026-129187 · Source: ENISA EUVD
- 2026-11-18 20:28 UTCEchelonGraph re-scoredFirst assessed: 7.3 HIGH
- 2026-11-18 20:27 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-130089?
When was the CVE record for CVE-2026-130089 published?
Is CVE-2026-130089 actively exploited?
What is the CVSS score of CVE-2026-130089?
How do I remediate CVE-2026-130089?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-130089
Is Your Infrastructure Affected by CVE-2026-130089?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.