CVE-2026-108126

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week
6.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Temporal Technologies Inc.) states them: "Upgrade to temporal-proxy 0.9.0 or later and set encryption.namespaceBinding to strict."

temporal-proxy 0.2.0 through 0.8.0 does not bind encrypted payloads to the namespace they were encrypted for. When payload encryption is enabled, the proxy chooses the decryption key by an identifier stored in the payload rather than by the namespace of the request, and nothing in the ciphertext records that namespace. A caller whom the proxy authorizes only for namespace B, and who has obtained an encrypted payload from namespace A, can therefore have the proxy decrypt it. In 0.8.0, the caller can submit the payload to the codec server's /decode endpoint. In every affected version, a caller who can also write to namespace B on the Temporal server directly can place the payload there and read it back through the proxy. This holds whether namespaces share the default key or each has its own, because a single proxy holds every key it is configured with. The issue does not give the attacker encrypted payloads they could not already obtain, and does not allow encrypted payloads to be modified.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity60% × 45%
Impact severity (EG Severity): CVSS 6.0 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.4%
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 (6.0): severity, escalated by confirmed exploitation. This CVE's 6.0 is its impact severity (EG Severity), not escalated.

EG Severity
6.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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.

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

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (9)

Auto-updated Oct 15, 2026
Patch available. Sources: github_commit, github_pr, github_release.
GitHub release Patch Available

0.9.0 Release

Patch available: temporalio/temporal-proxy v0.9.0

https://github.com/temporalio/temporal-proxy/releases/tag/v0.9.0
GitHub pull request Patch Available

[codecserver]: Bind payloads by the namespace the caller names

Patch available: temporalio/temporal-proxy v0.9.0 (PR #222 merged 2026-10-15)

https://github.com/temporalio/temporal-proxy/pull/222
GitHub pull request Patch Available

[crypto]: Bind sealed payloads to their namespace

Patch available: temporalio/temporal-proxy v0.9.0 (PR #221 merged 2026-10-15)

https://github.com/temporalio/temporal-proxy/pull/221
Web page

Use AAD in the payload encryption scheme · temporalio temporal-proxy · Discussion #146 · GitHub

https://github.com/temporalio/temporal-proxy/discussions/146
GitHub commit Patch Available

commit 6843a2c4626a (temporalio/temporal-proxy)

Patch available: temporalio/temporal-proxy v0.9.0 (contains commit 6843a2c4626a)

https://github.com/temporalio/temporal-proxy/commit/6843a2c4626aa2c7f00fbf54e4e9fa98f6254f07
GitHub commit Patch Available

commit 508991c298b9 (temporalio/temporal-proxy)

Patch available: temporalio/temporal-proxy v0.9.0 (contains commit 508991c298b9)

https://github.com/temporalio/temporal-proxy/commit/508991c298b9ac31915dd7349ffa88d79fad3475
Web page

temporal-proxy/pkg/crypto/vault.go at v0.8.0 · temporalio/temporal-proxy · GitHub

https://github.com/temporalio/temporal-proxy/blob/v0.8.0/pkg/crypto/vault.go#L256
Web page

temporal-proxy/pkg/crypto/kek.go at v0.8.0 · temporalio/temporal-proxy · GitHub

https://github.com/temporalio/temporal-proxy/blob/v0.8.0/pkg/crypto/kek.go#L172-L180
Web page

temporal-proxy/pkg/crypto/dek.go at v0.8.0 · temporalio/temporal-proxy · GitHub

https://github.com/temporalio/temporal-proxy/blob/v0.8.0/pkg/crypto/dek.go#L54-L67

Vendor Advisories for CVE-2026-108126(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 14× in last 7d / 14× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  5. 2026-10-18 05:07 UTCEG score recompute
  6. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  7. 2026-10-16 20:13 UTCGHSA enrichmentGHSA-vm4x-rqwp-c27m
  8. 2026-10-16 18:15 UTCEG score recompute
  9. 2026-10-16 18:15 UTCGHSA enrichmentGHSA-vm4x-rqwp-c27m
  10. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-16 16:01 UTCEG score recompute
  12. 2026-10-16 16:01 UTCGHSA enrichmentGHSA-vm4x-rqwp-c27m
  13. 2026-10-15 19:20 UTCEG score recomputeFirst assessed: 6.0 MEDIUM
  14. 2026-10-15 19:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-108126?
CVE-2026-108126 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. temporal-proxy 0.2.0 through 0.8.0 does not bind encrypted payloads to the namespace they were encrypted for. When payload encryption is enabled, the proxy chooses the decryption key by an identifier stored in the payload rather than by the namespace of the request, and nothing in the ciphertext…
When was the CVE record for CVE-2026-108126 published?
The CVE record for CVE-2026-108126 was published on October 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-108126 actively exploited?
CVE-2026-108126 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108126?
CVE-2026-108126 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108126?
A fix for CVE-2026-108126 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Temporal Technologies Inc.) states them: "Upgrade to temporal-proxy 0.9.0 or later and set encryption.namespaceBinding to strict." The vendor advisories EchelonGraph has for CVE-2026-108126 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-108126

Explore →

Is Your Infrastructure Affected by CVE-2026-108126?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs