opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0049, the 42nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 28 Oct 2026, 18:53 UTC Confirmed by the CVE List
2. 28 Oct 2026, 19:17 UTC Confirmed by NVD
3. 31 Oct 2026, 14:16 UTC First seen by agentprime
4. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-ccrj-gw8r-854m
• OSV: GHSA-ccrj-gw8r-854m
• github.com/open-telemetry/opentelemetry-java/security/advisories/GHSA-ccrj-gw8r-854m
• github.com/open-telemetry/opentelemetry-java/pull/8914
• github.com/open-telemetry/opentelemetry-java/commit/ba4dfea91647d1ef596975db5d7197681df3c0f5
• github.com/open-telemetry/opentelemetry-java/commit/cc4f5f22aed0d69369941cde8029e73507cf438f
• github.com/open-telemetry/opentelemetry-java
• github.com/open-telemetry/opentelemetry-java/releases/tag/v1.67.0

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.