How severe is GHSA-8785-wc3w-h8q6?

GHSA-8785-wc3w-h8q6 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8785-wc3w-h8q6?

GHSA-8785-wc3w-h8q6 affects the following packages: OpenTelemetry.Api (NuGet), OpenTelemetry.Api (NuGet), OpenTelemetry.Api (NuGet), OpenTelemetry.Api (NuGet), OpenTelemetry.Api (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-8785-wc3w-h8q6?

Update OpenTelemetry.Api to 1.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8785-wc3w-h8q6 is resolved across your whole dependency graph.

How do I detect GHSA-8785-wc3w-h8q6 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OpenTelemetry.Api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8785-wc3w-h8q6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8785-wc3w-h8q6?

O3 pinpoints whether GHSA-8785-wc3w-h8q6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8785-wc3w-h8q6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8785-wc3w-h8q6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8785-wc3w-h8q6?

GHSA-8785-wc3w-h8q6 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8785-wc3w-h8q6?

GHSA-8785-wc3w-h8q6 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8785-wc3w-h8q6 published, and has it been updated?

GHSA-8785-wc3w-h8q6 was published on March 5, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-8785-wc3w-h8q6

MEDIUM

OpenTelemetry .NET has Denial of Service (DoS) Vulnerability in API Package

Also known asCVE-2025-27513

Published

Mar 5, 2025

Updated

Feb 4, 2026

Affected

5 pkgs

Patched

1 / 5

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk37th percentile+0.42%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

5 pkgs affected

.NETOpenTelemetry.Api.NETOpenTelemetry.Api.NETOpenTelemetry.Api.NETOpenTelemetry.Api.NETOpenTelemetry.Api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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 resolved in OpenTelemetry.Api 1.11.2 by reverting the change that introduced the problematic behavior in versions 1.10.0 to 1.11.1.</li><li data-start="1290" data-end="1409">The fix ensures that valid tracing headers no longer cause excessive CPU consumption when received in requests.</li></ul><h4 data-start="1411" data-end="1434">Fixed Version:</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?

Affected Packages

5 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`OpenTelemetry.Api`	≥ 1.11.0&&< 1.11.2	1.11.2
.NETNuGet	`OpenTelemetry.Api`	all versions	No fix
.NETNuGet	`OpenTelemetry.Api`	all versions	No fix
.NETNuGet	`OpenTelemetry.Api`	all versions	No fix
.NETNuGet	`OpenTelemetry.Api`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OpenTelemetry.Api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update OpenTelemetry.Api to 1.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8785-wc3w-h8q6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8785-wc3w-h8q6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8785-wc3w-h8q6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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, deg

O3 Security · Impact-Aware SCA

Is GHSA-8785-wc3w-h8q6 in your dependencies?

O3 detects GHSA-8785-wc3w-h8q6 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-8785-wc3w-h8q6

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-8785-wc3w-h8q6 in your dependencies?