CVE-2026-41178: CWE-789: Memory Allocation with Excessive Size Value in open-telemetry go.opentelemetry.io/otel/baggage
OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes `Parse` to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-41178 affects the OpenTelemetry-Go implementation, specifically the baggage package. In versions 1.41.0 and 1.43.0, the removal of raw-length rejection allowed the Parse function to accept and process excessively large or invalid baggage headers. This can cause memory allocation with excessive size values, leading to denial of service conditions due to resource exhaustion. The issue is addressed in versions 1.42.0 and 1.44.0, which restore proper validation and mitigate the risk. The CVSS 3.1 score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, no user interaction, and impact limited to availability.
Potential Impact
The vulnerability enables denial of service attacks by allowing an attacker to send oversized baggage headers that cause excessive memory allocation in the affected OpenTelemetry-Go versions. This impacts the availability of services using these specific versions (1.41.0 and 1.43.0) but does not affect confidentiality or integrity. There are no known exploits in the wild at this time.
Mitigation Recommendations
Versions 1.42.0 and 1.44.0 of OpenTelemetry-Go have fixed this vulnerability by restoring raw-length rejection and proper validation of baggage headers. Users should upgrade to these or later versions to mitigate the risk. Patch status is not explicitly confirmed in the provided data; therefore, users should consult the official OpenTelemetry project advisories or repositories for the latest remediation information. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-41178: CWE-789: Memory Allocation with Excessive Size Value in open-telemetry go.opentelemetry.io/otel/baggage
Description
OpenTelemetry-Go is the Go implementation of OpenTelemetry. Versions 1.41.0 and 1.43.0 removed raw-length rejection and it causes `Parse` to process arbitrarily large/invalid baggage headers and log errors, enabling DoS via oversized inputs. Versions 1.42.0 and 1.44.0 fix the issue.
CVSS v3.1
Score 5.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-41178 affects the OpenTelemetry-Go implementation, specifically the baggage package. In versions 1.41.0 and 1.43.0, the removal of raw-length rejection allowed the Parse function to accept and process excessively large or invalid baggage headers. This can cause memory allocation with excessive size values, leading to denial of service conditions due to resource exhaustion. The issue is addressed in versions 1.42.0 and 1.44.0, which restore proper validation and mitigate the risk. The CVSS 3.1 score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges required, no user interaction, and impact limited to availability.
Potential Impact
The vulnerability enables denial of service attacks by allowing an attacker to send oversized baggage headers that cause excessive memory allocation in the affected OpenTelemetry-Go versions. This impacts the availability of services using these specific versions (1.41.0 and 1.43.0) but does not affect confidentiality or integrity. There are no known exploits in the wild at this time.
Mitigation Recommendations
Versions 1.42.0 and 1.44.0 of OpenTelemetry-Go have fixed this vulnerability by restoring raw-length rejection and proper validation of baggage headers. Users should upgrade to these or later versions to mitigate the risk. Patch status is not explicitly confirmed in the provided data; therefore, users should consult the official OpenTelemetry project advisories or repositories for the latest remediation information. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-17T16:34:45.526Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a219e6ae29bf47b50b44766
Added to database: 6/4/2026, 3:48:58 PM
Last enriched: 6/4/2026, 4:03:50 PM
Last updated: 6/4/2026, 5:04:04 PM
Views: 6
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.