CVE-2025-27513
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.51 % · percentile 43.84 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
OpenTelemetry dotnet is a dotnet telemetry framework. A vulnerability in OpenTelemetry.Api package 1.10.0 to 1.11.1 could cause a Denial of Service (DoS) when a tracestate and traceparent header is received. Even if an application does not explicitly use trace context propagation, receiving these headers can still trigger high CPU usage. This issue impacts any application accessible over the web or backend services that process HTTP requests containing a tracestate header. Application may experience excessive resource consumption, leading to increased latency, degraded performance, or downtime. This vulnerability is fixed in 1.11.2.
Read the publisher's advisoryOpenTelemetry dotnet is a dotnet telemetry framework. A vulnerability in OpenTelemetry.Api package 1.10.0 to 1.11.1 could cause a Denial of Service (DoS) when a tracestate and traceparent header is received. Even if an application does not explicitly use trace context propagation, receiving these headers can still trigger high CPU usage. This issue impacts any application accessible over the web or backend services that process HTTP requests containing a tracestate header. Application may experience excessive resource consumption, leading to increased latency, degraded performance, or downtime. This vulnerability is fixed in 1.11.2.
Read the publisher's advisoryOpenTelemetry dotnet is a dotnet telemetry framework. A vulnerability in OpenTelemetry.Api package 1.10.0 to 1.11.1 could cause a Denial of Service (DoS) when a tracestate and traceparent header is received. Even if an application does not explicitly use trace context propagation, receiving these headers can still trigger high CPU usage. This issue impacts any application accessible over the web or backend services that process HTTP requests containing a tracestate header. Application may experience excessive resource consumption, leading to increased latency, degraded performance, or downtime. This vulnerability is fixed in 1.11.2.
Read the publisher's advisory### Impact _What kind of vulnerability is it? Who is impacted?_ A vulnerability in `OpenTelemetry.Api` package `1.10.0` to `1.11.1` could cause a Denial of Service (DoS) when a `tracestate` and `traceparent` header is received. * Even if an application does not explicitly use trace context propagation, receiving these headers can still trigger high CPU usage. * This issue impacts any application accessible over the web or backend services that process HTTP requests containing a `tracestate` header. * Application may experience excessive resource consumption, leading to increased latency, degraded performance, or downtime. ### Patches _Has the problem been patched? What versions should users upgrade to?_ This issue has been <strong data-start="1143" data-end="1184">resolved in OpenTelemetry.Api 1.11.2</strong> by <strong data-start="1188" data-end="1212">reverting the change</strong> that introduced the problematic behavior in versions <strong data-start="1266" data-end="1286">1.10.0 to 1.11.1</strong>.</li><li data-start="1290" data-end="1409">The fix ensures that <strong data-start="1313" data-end="1380">valid tracing headers no longer cause excessive CPU consumption</strong> when received in requests.</li></ul><h4 data-start="1411" data-end="1434"><strong data-start="1416" data-end="1434">Fixed Version:</strong></h4> OpenTelemetry .NET Version | Status -- | -- <= 1.9.x | ✅ Not affected 1.10.0 - 1.11.1 | ❌ Vulnerable 1.11.2 (Fixed) | ✅ Safe to use **Upgrade Command:** ``` dotnet add package OpenTelemetry --version 1.11.2 ``` **Delisting of Affected Packages** To prevent accidental usage, we have delisted the affected versions (1.10.0 to 1.11.1) from NuGet. Users should avoid these versions and upgrade to 1.11.2 immediately. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ ### References _Are there any links users can visit to find out more?_
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.51 % · percentile 43.84 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2025-27513 · 15 Nov 2026 14:45:34 UTC
CVE-2025-27513 · 14 Nov 2026 16:37:01 UTC
CVE-2025-27513 · 13 Nov 2026 19:59:34 UTC
CVE-2025-27513 · 12 Nov 2026 18:18:51 UTC
CVE-2025-27513 · 10 Nov 2026 20:24:10 UTC
CVE-2025-27513 · 09 Nov 2026 21:04:24 UTC
CVE-2025-27513 · 08 Nov 2026 15:12:21 UTC
CVE-2025-27513 · 07 Nov 2026 16:07:52 UTC
CVE-2025-27513 · 06 Nov 2026 19:10:17 UTC
CVE-2025-27513 · 05 Nov 2026 22:49:22 UTC
CVE-2025-27513 · 05 Nov 2026 02:54:06 UTC
CVE-2025-27513 · 03 Nov 2026 16:59:18 UTC
CVE-2025-27513 · 02 Nov 2026 23:59:04 UTC
CVE-2025-27513 · 01 Nov 2026 23:58:58 UTC
CVE-2025-27513 · 01 Nov 2026 03:04:52 UTC
CVE-2025-27513 · 31 Oct 2026 01:52:30 UTC
CVE-2025-27513 · 29 Oct 2026 18:29:26 UTC
CVE-2025-27513 · 28 Oct 2026 19:55:37 UTC
CVE-2025-27513 · 27 Oct 2026 15:46:19 UTC
CVE-2025-27513 · 27 Oct 2026 00:23:05 UTC
CVE-2025-27513 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
euvd · EUVD-2025-6151 · Published
nvd · CVE-2025-27513 · Published
osv · GHSA-8785-wc3w-h8q6 · Published
cve-program · CVE-2025-27513 · Published