Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-40894: CWE-789: Memory Allocation with Excessive Size Value in open-telemetry opentelemetry-dotnet

0
Medium
VulnerabilityCVE-2026-40894cvecve-2026-40894cwe-789
Published: Thu Apr 23 2026 (04/23/2026, 18:03:28 UTC)
Source: CVE Database V5
Vendor/Project: open-telemetry
Product: opentelemetry-dotnet

Description

OpenTelemetry dotnet is a dotnet telemetry framework. In OpenTelemetry.Api 0.5.0-beta.2 to 1.15.2 and OpenTelemetry.Extensions.Propagators 1.3.1 to 1.15.2, The implementation details of the baggage, B3 and Jaeger processing code in the OpenTelemetry.Api and OpenTelemetry.Extensions.Propagators NuGet packages can allocate excessive memory when parsing which could create a potential denial of service (DoS) in the consuming application. This vulnerability is fixed in 1.15.3.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/23/2026, 19:06:43 UTC

Technical Analysis

CVE-2026-40894 describes a memory allocation vulnerability (CWE-789) in the OpenTelemetry.Api and OpenTelemetry.Extensions.Propagators NuGet packages for .NET. Specifically, versions from 0.5.0-beta.2 up to but not including 1.15.3 contain parsing code for baggage, B3, and Jaeger that may allocate excessive memory, which could be exploited to cause a denial of service in the consuming application. The vulnerability has a CVSS 3.1 base score of 5.3, indicating medium severity, with no impact on confidentiality or integrity but an impact on availability. The vulnerability is fixed in version 1.15.3.

Potential Impact

The vulnerability can cause a denial of service by exhausting memory resources due to excessive memory allocation during parsing operations in the affected OpenTelemetry dotnet packages. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.

Mitigation Recommendations

Upgrade affected OpenTelemetry dotnet packages to version 1.15.3 or later, where this vulnerability is fixed. Since this is a library used in applications, updating dependencies to the patched version is the recommended remediation. Patch status is confirmed fixed in 1.15.3.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-15T16:37:22.766Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69ea6a1a87115cfb68455b93

Added to database: 4/23/2026, 6:51:06 PM

Last enriched: 4/23/2026, 7:06:43 PM

Last updated: 4/24/2026, 6:06:33 AM

Views: 19

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses