CVE-2026-128086VulnerabilityPublished 13 Nov 2026

go.opentelemetry.io/otel/baggage · OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification

Affects go.opentelemetry.io/otel/baggageSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-41178

Authoritative record:CVE-2026-128086· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.47.0 when convenient.

Data as of 13 Nov 2026, 20:19 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	5.3

Patch: Available – fixed in 1.47.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade go.opentelemetry.io/otel/baggage and go.opentelemetry.io/otel/propagation to 1.47.0.

Affected software

Product	Affected	Fixed in
Gogo.opentelemetry.io/otel/baggage	Affected >=1.0.0-RC1 <1.47.0	Fixed in 1.47.0
Gogo.opentelemetry.io/otel/propagation	Affected >=1.0.0-RC1 <1.47.0	Fixed in 1.47.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in OpenTelemetry-Go version 1.47.0. Users should upgrade to version 1.47.0 or later, which implements in-place validation and normalization of W3C property metadata and lazy materialization of Property structs to prevent allocation amplification. Additionally, ensure that baggage propagation is enabled only when necessary and that HTTP handlers extracting baggage are placed appropriately in the request handling chain, preferably after authentication, to reduce exposure to attacker-controlled input.

Description

OpenTelemetry-Go versions from 1.0.0-RC1 up to but not including 1.47.0 contain a vulnerability in the baggage metadata parsing implementation. The library eagerly materializes W3C baggage properties during parsing, causing bounded but disproportionate memory allocation amplification when processing densely populated headers. This can lead to increased memory allocation and garbage collection pressure, especially on services that enable baggage propagation and extract attacker-controlled context before authentication. The issue does not reliably cause out-of-memory conditions or complete denial of service. The vulnerability is fixed in version 1.47.0 by introducing lazy materialization of properties and in-place validation and normalization.

Impact

This vulnerability causes increased memory allocation and garbage collection pressure due to allocation amplification when parsing large, densely populated W3C baggage headers. While it can increase resource consumption and potentially degrade performance under concurrent or sustained requests, it does not reliably cause out-of-memory conditions, process termination, or complete denial of service. There is no impact on confidentiality or integrity. The vulnerability is limited to services that enable baggage propagation and extract attacker-controlled inbound context before authentication or on public routes.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-405Asymmetric Resource Consumption (Amplification) (opens in a new tab)
Class weakness
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
Architecture and Design
An application must make resources available to a client commensurate with the client's access level.
Architecture and Design
An application must, at all times, keep track of allocated resources and meter their usage appropriately.
System Configuration
Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 20:19 UTC

WeaknessesCWE-400, CWE-405

Technical details

References

Community reviews

Related threats