A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.
CVE-2026-130091
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-129188 (ENISA EUVD) · GHSA-mhcr-64cf-9g9r (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
Fixed versions, as the CVE record's CNA (Temporal Technologies Inc.) states them: "Upgrade to temporal-proxy 1.2.1 or later."
- CVSS
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 32EG Risk 32/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)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 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.5%
- EPSS %ILE
- 41st
- 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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.5% 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 (7)
Auto-updated Nov 18, 20261.2.1 Release
Patch available: temporalio/temporal-proxy v1.2.1
https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1commit 5c5060cc77c8 (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit 5c5060cc77c8 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/5c5060cc77c8e94a01de1414cc32e55751580381[proxy]: Bound decoded bytes per response and in flight (#295)
Fix merged in temporalio/temporal-proxy PR #301 on 2026-11-18 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/301commit ea70ede864cd (temporalio/temporal-proxy)
Fix landed in temporalio/temporal-proxy commit ea70ede864cd — awaiting tagged release
https://github.com/temporalio/temporal-proxy/commit/ea70ede864cdf6aa9591432d0464a6d6f3413260[proxy]: Bound decoded bytes per response and in flight
Fix merged in temporalio/temporal-proxy PR #295 on 2026-11-18 — awaiting tagged release
https://github.com/temporalio/temporal-proxy/pull/295temporal-proxy/pkg/codec/compressor.go at v1.2.0 · temporalio/temporal-proxy · GitHub
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/pkg/codec/compressor.go#L206-L262temporal-proxy/internal/proxy/codec.go at v1.2.0 · temporalio/temporal-proxy · GitHub
https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/codec.go#L157-L166Vendor Advisories for CVE-2026-130091(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.5% · 41st percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-20 01:27 UTCEchelonGraph re-scored
- 2026-11-20 01:27 UTCGHSA enrichmentGHSA-mhcr-64cf-9g9r · GitHub severity HIGH
- 2026-11-19 20:56 UTCOSV refresh
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-18 22:28 UTCGHSA enrichmentGHSA-mhcr-64cf-9g9r · GitHub severity HIGH
- 2026-11-18 21:46 UTCGHSA enrichmentGHSA-mhcr-64cf-9g9r · GitHub severity HIGH
- 2026-11-18 21:28 UTCEchelonGraph re-scored
- 2026-11-18 21:03 UTCENISA EUVD ID recordedEUVD-2026-129188 · Source: ENISA EUVD
- 2026-11-18 20:33 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
- 2026-11-18 20:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-130091?
When was the CVE record for CVE-2026-130091 published?
Is CVE-2026-130091 actively exploited?
What is the CVSS score of CVE-2026-130091?
How do I remediate CVE-2026-130091?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-130091
Is Your Infrastructure Affected by CVE-2026-130091?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.