https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 09:50:31 +0000 https://vulnerability.circl.lu/vuln/cve-2026-29181 <p><strong>Affected:</strong> open-telemetry opentelemetry-go, Red Hat Cert Manager support for Red Hat OpenShift release 1.19, Red Hat Cluster Observability Operator 1.5.0, Red Hat Logging Subsystem for Red Hat OpenShift 6.6, Red Hat multicluster engine for Kubernetes 2.11, Red Hat multicluster engine for Kubernetes 2.8, Red Hat cert-manager Operator for Red Hat OpenShift, Red Hat Multicluster Engine for Kubernetes, Red Hat Advanced Cluster Management for Kubernetes 2</p> <p>OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.36.0 to 1.40.0, multi-value baggage: header extraction parses each header field-value independently and aggregates members across values. This allows an attacker to amplify cpu and allocations by sending many baggage: header lines, even when each individual value is within the 8192-byte per-value parse limit. This vulnerability is fixed in 1.41.0.</p> <p><strong>Affected:</strong> open-telemetry opentelemetry-go, Red Hat Cert Manager support for Red Hat OpenShift release 1.19, Red Hat Cluster Observability Operator 1.5.0, Red Hat Logging Subsystem for Red Hat OpenShift 6.6, Red Hat multicluster engine for Kubernetes 2.11, Red Hat multicluster engine for Kubernetes 2.8, Red Hat cert-manager Operator for Red Hat OpenShift, Red Hat Multicluster Engine for Kubernetes, Red Hat Advanced Cluster Management for Kubernetes 2</p> <p>OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.36.0 to 1.40.0, multi-value baggage: header extraction parses each header field-value independently and aggregates members across values. This allows an attacker to amplify cpu and allocations by sending many baggage: header lines, even when each individual value is within the 8192-byte per-value parse limit. This vulnerability is fixed in 1.41.0.</p> https://vulnerability.circl.lu/vuln/cve-2026-29181 https://vulnerability.circl.lu/vuln/ghsa-mh2q-q3fh-2475 <p><strong>Affected:</strong> Go: go.opentelemetry.io/otel</p> <p>multi-value `baggage:` header extraction parses each header field-value independently and aggregates members across values. this allows an attacker to amplify cpu and allocations by sending many `baggage:` header lines, even when each individual value is within the 8192-byte per-value parse limit.</p> <p>## severity</p> <p>HIGH (availability / remote request amplification)</p> <p>## relevant links</p> <p>- repository: https://github.com/open-telemetry/opentelemetry-go - pinned callsite: https://github.com/open-telemetry/opentelemetry-go/blob/1ee4a4126dbdd1bc79e9fae072fa488beffac52a/propagation/baggage.go#L58</p> <p>## vulnerability details</p> <p>**pins:** open-telemetry/opentelemetry-go@1ee4a4126dbdd1bc79e9fae072fa488beffac52a **as-of:** 2026-02-04 **policy:** direct (no program scope provided)</p> <p>**callsite:** propagation/baggage.go:58 (`extractMultiBaggage`) **attacker control:** inbound HTTP request headers (many `baggage` field-values) → `propagation.HeaderCarrier.Values(&#34;baggage&#34;)` → repeated `baggage.Parse` + member aggregation</p> <p>### root cause</p> <p>`extractMultiBaggage` iterates over all `baggage` header field-values and parses each one independently, then appends members into a shared slice. the 8192-byte parsing cap applies per header value, but the multi-value path repeats that work once per header line (bounded only by the server/proxy header byte limit).</p> <p>### impact</p> <p>in a default `net/http` configuration (max header bytes 1mb), a single request with many `baggage:` header field-values can cause large per…</p> <p><strong>Affected:</strong> Go: go.opentelemetry.io/otel</p> <p>multi-value `baggage:` header extraction parses each header field-value independently and aggregates members across values. this allows an attacker to amplify cpu and allocations by sending many `baggage:` header lines, even when each individual value is within the 8192-byte per-value parse limit.</p> <p>## severity</p> <p>HIGH (availability / remote request amplification)</p> <p>## relevant links</p> <p>- repository: https://github.com/open-telemetry/opentelemetry-go - pinned callsite: https://github.com/open-telemetry/opentelemetry-go/blob/1ee4a4126dbdd1bc79e9fae072fa488beffac52a/propagation/baggage.go#L58</p> <p>## vulnerability details</p> <p>**pins:** open-telemetry/opentelemetry-go@1ee4a4126dbdd1bc79e9fae072fa488beffac52a **as-of:** 2026-02-04 **policy:** direct (no program scope provided)</p> <p>**callsite:** propagation/baggage.go:58 (`extractMultiBaggage`) **attacker control:** inbound HTTP request headers (many `baggage` field-values) → `propagation.HeaderCarrier.Values(&#34;baggage&#34;)` → repeated `baggage.Parse` + member aggregation</p> <p>### root cause</p> <p>`extractMultiBaggage` iterates over all `baggage` header field-values and parses each one independently, then appends members into a shared slice. the 8192-byte parsing cap applies per header value, but the multi-value path repeats that work once per header line (bounded only by the server/proxy header byte limit).</p> <p>### impact</p> <p>in a default `net/http` configuration (max header bytes 1mb), a single request with many `baggage:` header field-values can cause large per…</p> https://vulnerability.circl.lu/vuln/ghsa-mh2q-q3fh-2475