CVE-2026-118259

opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.67.0, W3CTraceContextPropagator.extract() uses regex delimiter processing that can exhibit quadratic backtracking while parsing tracestate headers containing long runs of spaces or tabs without a following comma. An unauthenticated attacker whose headers reach extraction can repeatedly block request or event-loop threads and cause excessive CPU consumption, with practical impact bounded by ingress header-size limits, proxy configuration, and threading. This issue is fixed in version 1.67.0.

Analysis

AI-generated

Technical impact

W3CTraceContextPropagator.extract() in opentelemetry-java performed regex parsing of the tracestate header that can exhibit quadratic backtracking when the header contains long sequences of spaces or tabs without a following comma. An unauthenticated attacker can supply such a header and repeatedly block request or event‑loop threads, leading to high CPU usage. The primary impact is a denial‑of‑service condition and possible exhaustion of processing resources for a target application.

Affected Systems

The vulnerability affects the open-telemetry:opentelemetry-java implementation of the OpenTelemetry API and SDK. All releases earlier than 1.67.0 contain the issue. Updating to version 1.67.0 or later removes the affected code path.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity. Exploitation requires the ability to supply custom tracestate headers in incoming requests; authentication is not required. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is an external attacker sending malicious HTTP headers, which can be abused if no header size restrictions or input validation are in place.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade opentelemetry-java to version 1.67.0 or later.
  • Reconfigure proxies or load balancers to enforce strict header size limits on W3C tracestate headers.
  • Monitor CPU usage for anomalous spikes correlated with incoming requests to detect potential exploitation.

Generated by OpenCVE AI on October 28, 2026 at 20:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-ccrj-gw8r-854m opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Opentelemetry
Opentelemetry opentelemetry-java
Vendors & Products Opentelemetry
Opentelemetry opentelemetry-java
Type Values Removed Values Added
Description opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.67.0, W3CTraceContextPropagator.extract() uses regex delimiter processing that can exhibit quadratic backtracking while parsing tracestate headers containing long runs of spaces or tabs without a following comma. An unauthenticated attacker whose headers reach extraction can repeatedly block request or event-loop threads and cause excessive CPU consumption, with practical impact bounded by ingress header-size limits, proxy configuration, and threading. This issue is fixed in version 1.67.0.
Title opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing
Weaknesses CWE-1333
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-1333

    Inefficient Regular Expression Complexity

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 2, 2026, 8:30 PM
Reserved
Oct 27, 2026, 8:13 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 7:17 PM
Modified
Nov 2, 2026, 9:17 PM