Vulnerability · CVE-2026-118259
opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing
Published Oct 28, 2026 · catalog updated Oct 28, 2026 · opentelemetry-java: Quadratic CPU consumption
Last checked Nov 7, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-118259. EPSS is 0.49%. Act only if a listed version of opentelemetry-java: Quadratic CPU consumption is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (opentelemetry-java: Quadratic CPU consumption).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.49%
- Remediation
- Advisory link
- Affected products
- Maven io.opentelemetry:opentelemetry-api · maven io.opentelemetry
### Summary OpenTelemetry Java's W3C trace-context propagator permits excessive CPU consumption when extracting crafted headers, potentially leading to denial of service. Regex backtracking causes quadratic parsing time for headers containing long runs of spaces or tabs without a following comma. ### Impact An unauthenticated attacker whose headers reach can cause excessive CPU usage through crafted requests. Parsing blocks the calling thread, potentially affecting other connections when extraction runs on a shared event-loop thread. Actual impact depends on ingress header-size limits, proxy configuration, and threading. Header-size limits reduce the per-request cost but do not eliminate the vulnerability. ### Patches Upgrade to version **1.67.0** or later. [PR #8914](https://github.com/open-telemetry/opentelemetry-java/pull/8914) replaces regex delimiter splitting with literal comma scanning and explicit whitespace trimming. ### Workarounds If upgrading is not possible, reject or remove oversized headers before trace-context extraction. This reduces the per-request parsing cost but does not eliminate the risk from repeated requests.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Maven io.opentelemetry:opentelemetry-api0 → 1.67.0
- maven io.opentelemetryversion unspecified
How to fix CVE-2026-118259
Upgrade
CVE-2026-118259 lists a fix boundary at 1.67.0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 1.67.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-118259. EPSS is 0.49%. Act only if a listed version of opentelemetry-java: Quadratic CPU consumption is installed.
Which versions are affected?
Compare what you have installed with 0 → 1.67.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-1333: Inefficient Regular Expression Complexity. EPSS 0.49%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 28, 2026 · GitHub Advisory Database
Detected
### Summary OpenTelemetry Java's W3C trace-context propagator permits excessive CPU consumption when extracting crafted headers, potentially leading to denial of service. Regex backtracking causes quadratic parsing time for headers containing long runs of spaces or tabs without a following comma. ### Impact An unauthenticated attacker whose headers reach can cause excessive CPU usage through craft
Oct 28, 2026 · GitHub Advisory Database
Fix available
io.opentelemetry:opentelemetry-api fixed in 1.67.0
Oct 28, 2026 · GitHub Advisory Database
Fix available
io.opentelemetry:opentelemetry-api fixed in 1.67.0
Oct 28, 2026 · GitHub Advisory Database
Updated
### Summary OpenTelemetry Java's W3C trace-context propagator permits excessive CPU consumption when extracting crafted headers, potentially leading to denial of service. Regex backtracking causes quadratic parsing time for headers containing long runs of spaces or tabs without a following comma. ### Impact An unauthenticated attacker whose headers reach can cause excessive CPU usage through craft
Sources
- CVE.orgVulnerability recordCVE-2026-118259
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-118259
30-day exploitation probability 0.49%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-ccrj-gw8r-854m
GitHub Advisory Database record mirrored by OSV.
github.com - GitLab Advisory DatabasePackage advisoryCVE-2026-118259
OpenTelemetry Java's W3C trace-context propagator permits excessive CPU consumption when extracting crafted tracestate headers, potentially leading to denial of service. Regex backtracking causes quadratic parsing time for headers containing long runs of spaces or tabs without a following comma.
advisories.gitlab.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-ccrj-gw8r-854m
opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing
osv.dev
References
Freshness
Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 7, 2026
- CVE.orgOct 29, 2026
- GitLab Advisory DatabaseOct 29, 2026
- GitHub Advisory DatabaseOct 29, 2026
- OpenSSF OSV / OSV ScannerOct 29, 2026