CVE-2026-114603

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

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

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-10-22. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-108216 (ENISA EUVD) · GHSA-xcq7-p3pf-p88h (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.1, the opentelemetry-api function TraceState.from_header in opentelemetry/trace/span.py, reached through TraceContextTextMapPropagator.extract, parses inbound W3C tracestate headers with an unbounded optional-whitespace regular expression. A malformed header containing a long run of spaces or tabs without a following comma causes quadratic backtracking before the member-count limit is applied. Services using the default W3C Trace Context propagator can therefore spend excessive CPU time on one unauthenticated request when the HTTP server, parser, gateway, or custom carrier accepts a sufficiently large header. The processing can occupy a synchronous worker or delay unrelated requests on the same asynchronous event loop. The impact is limited to availability and does not expose or modify telemetry data or allow code execution. This issue is fixed in version 1.45.1.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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.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).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

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

October 22, 2026

Last Modified

October 29, 2026

Advisory Details (5)

Auto-updated Oct 22, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

Version 1.45.1/0.66b1

Patch available: open-telemetry/opentelemetry-python v1.45.1

https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.1
Web page

opentelemetry-python/CHANGELOG.md at main · open-telemetry/opentelemetry-python · GitHub

https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md#version-1451066b1-2026-10-06
GitHub commit Patch Available

commit d5224bf4ffdf (open-telemetry/opentelemetry-python)

Patch available: open-telemetry/opentelemetry-python v1.45.1 (contains commit d5224bf4ffdf)

https://github.com/open-telemetry/opentelemetry-python/commit/d5224bf4ffdf2aee1b592ad238dcc32ca957f26b
GitHub pull request Patch Available

[release/v1.45.x-0.66bx] opentelemetry-api: improve performance of tracestate parsing

Patch available: open-telemetry/opentelemetry-python v1.45.1 (PR #5749 merged 2026-10-06)

https://github.com/open-telemetry/opentelemetry-python/pull/5749
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unbounded tracestate parsing in opentelemetry-api · Advisory · open-telemetry/opentelemetry-python · GitHub

https://github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-xcq7-p3pf-p88h

Vendor Advisories for CVE-2026-114603(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipopentelemetry-api @ 1.45.1 (fixes <= 1.45.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
opentelemetry-api0.10b0 ... 1.9.1 (85 versions)
  • every version up to 1.45.1: fixed in 1.45.1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 18× 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-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-xcq7-p3pf-p88h · GitHub severity MODERATE · GitHub CVSS 5.3
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-29 04:29 UTCEG score recompute
  8. 2026-10-29 02:25 UTCEG score recompute
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-25 14:50 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-22 16:28 UTCEG score recompute
  17. 2026-10-22 15:37 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  18. 2026-10-22 15:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-114603?
CVE-2026-114603 is a medium-severity vulnerability; its CVE record was published on October 22, 2026. OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.1, the opentelemetry-api function TraceState.from_header in opentelemetry/trace/span.py, reached through TraceContextTextMapPropagator.extract, parses inbound W3C tracestate headers with an unbounded…
When was the CVE record for CVE-2026-114603 published?
The CVE record for CVE-2026-114603 was published on October 22, 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 29, 2026; the record at its source may have been updated since.
Is CVE-2026-114603 actively exploited?
CVE-2026-114603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114603?
CVE-2026-114603 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114603?
A fix for CVE-2026-114603 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114603 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-114603

Explore →

Is Your Infrastructure Affected by CVE-2026-114603?

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