CVE-2026-118259: opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing

Published Oct 28, 2026
·
Updated

Summary

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.

Impact

An unauthenticated attacker whose headers reach W3CTraceContextPropagator.extract() 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 io.opentelemetry:opentelemetry-api to version 1.67.0 or later. PR #8914 replaces regex delimiter splitting with literal comma scanning and explicit whitespace trimming.

Workarounds

If upgrading is not possible, reject or remove oversized tracestate headers before trace-context extraction. This reduces the per-request parsing cost but does not eliminate the risk from repeated requests.

Other sources

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.

— MITRE

Affected Software

4 affected componentsFixes available
maven/io.opentelemetry/opentelemetry-api<1.67.0
maven/io.opentelemetry:opentelemetry-api<=1.66.0
1.67.0
maven/io.opentelemetry:opentelemetry-api<1.67.0
1.67.0
IBM API Connect<=V10.0.8.0 - V10.0.8.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.opentelemetry:opentelemetry-api to a version that resolves this vulnerability.

    Fixed in 1.67.0
  2. Upgrade

    Upgrade io.opentelemetry:opentelemetry-api to a version that resolves this vulnerability.

    Fixed in 1.67.0
  3. Compensating control

    Reject or remove oversized tracestate headers before W3C trace-context extraction if upgrading is not possible

Event History

Oct 28, 2026
CVE Published
via MITRE·06:53 PM
Data Sourced
via MITRE·06:53 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:07 PM
Data Sourced
via GitHub·09:07 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·09:07 PM
Affected Software
Nov 18, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using opentelemetry-java versions before 1.67.0 are exposed when attacker-controlled request headers reach W3CTraceContextPropagator.extract(). The practical impact depends on ingress header-size limits, proxy configuration, and available request or event-loop threads.

2

What does an attacker need to send to trigger the CPU consumption?

An unauthenticated attacker needs to supply a tracestate header containing a long run of spaces or tabs with no following comma, and have that header processed by extraction. Repeated requests can block request or event-loop threads and consume excessive CPU.

3

What can be done if upgrading is not immediately possible?

Limit the size of inbound headers and use proxy or ingress configuration to prevent oversized or malformed tracestate headers from reaching the application. Threading configuration also bounds the practical impact of repeated requests.

4

How can I determine whether a deployment is affected?

Check whether the application uses opentelemetry-java earlier than 1.67.0 and whether inbound headers can reach W3CTraceContextPropagator.extract(). Systems that accept externally controlled tracestate headers are the relevant exposure path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203