CVE-2026-40891: CWE-789: Memory Allocation with Excessive Size Value in open-telemetry opentelemetry-dotnet
OpenTelemetry dotnet is a dotnet telemetry framework. From 1.13.1 to before 1.15.2, When exporting telemetry over gRPC using the OpenTelemetry Protocol (OTLP), the exporter may parse a server-provided grpc-status-details-bin trailer during retry handling. Prior to the fix, a malformed trailer could encode an extremely large length-delimited protobuf field which was used directly for allocation, allowing excessive memory allocation and potential denial of service (DoS). This vulnerability is fixed in 1.15.2.
AI Analysis
Technical Summary
OpenTelemetry dotnet versions from 1.13.1 to before 1.15.2 contain a vulnerability (CWE-789) related to memory allocation with an excessive size value. When exporting telemetry data over gRPC using OTLP, the exporter parses a server-provided grpc-status-details-bin trailer during retry handling. A malformed trailer can encode an extremely large length-delimited protobuf field, which the exporter uses directly for memory allocation without adequate validation. This can cause excessive memory allocation, resulting in a denial of service condition. The issue is resolved in version 1.15.2.
Potential Impact
An attacker able to influence the grpc-status-details-bin trailer during telemetry export can cause the vulnerable OpenTelemetry dotnet exporter to allocate excessive memory, potentially leading to denial of service. There is no impact on confidentiality or integrity. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade OpenTelemetry dotnet to version 1.15.2 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 1.15.2. No other mitigations are specified.
CVE-2026-40891: CWE-789: Memory Allocation with Excessive Size Value in open-telemetry opentelemetry-dotnet
Description
OpenTelemetry dotnet is a dotnet telemetry framework. From 1.13.1 to before 1.15.2, When exporting telemetry over gRPC using the OpenTelemetry Protocol (OTLP), the exporter may parse a server-provided grpc-status-details-bin trailer during retry handling. Prior to the fix, a malformed trailer could encode an extremely large length-delimited protobuf field which was used directly for allocation, allowing excessive memory allocation and potential denial of service (DoS). This vulnerability is fixed in 1.15.2.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenTelemetry dotnet versions from 1.13.1 to before 1.15.2 contain a vulnerability (CWE-789) related to memory allocation with an excessive size value. When exporting telemetry data over gRPC using OTLP, the exporter parses a server-provided grpc-status-details-bin trailer during retry handling. A malformed trailer can encode an extremely large length-delimited protobuf field, which the exporter uses directly for memory allocation without adequate validation. This can cause excessive memory allocation, resulting in a denial of service condition. The issue is resolved in version 1.15.2.
Potential Impact
An attacker able to influence the grpc-status-details-bin trailer during telemetry export can cause the vulnerable OpenTelemetry dotnet exporter to allocate excessive memory, potentially leading to denial of service. There is no impact on confidentiality or integrity. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade OpenTelemetry dotnet to version 1.15.2 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 1.15.2. No other mitigations are specified.
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: 69ea5fae87115cfb683e85c7
Added to database: 4/23/2026, 6:06:38 PM
Last enriched: 4/23/2026, 6:21:14 PM
Last updated: 4/25/2026, 6:54:27 AM
Views: 19
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.