CVE-2026-29181 — OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)

Affected: 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

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.

GHSA-hr2v-4r36-88hr — Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment

Affected: Go: helm.sh/helm/v4, Go: helm.sh/helm/v3

Helm is a package manager for Charts for Kubernetes. In Helm versions <=3.20.1 and <=4.1.3, a specially crafted Chart will cause `helm pull --untar [chart URL | repo/chartname]` to write the Chart's contents to the immediate output directory (as defaulted to the current working directory; or as given by the `--destination` and `--untardir` flags), rather than the expected output directory suffixed by the chart's name.

### Impact

The bug enables writing the Chart's contents (unpackaged/untar'ed) to the output directory `<output dir>/`, instead of the expected `<output dir>/<chart name>/`, potentially overwriting the contents of the targeted directory.

Note: a chart name containing POSIX dot-dot, or dot-dot and slashes (as if to refer to parent directories) do not resolve beyond the output directory as designed.

### Patches

This issue has been resolved in Helm v3.20.2 and v4.1.3

A Chart with an unexpected name (those specified to be "." or ".."), or a Chart name which results in a non-unique directory will be rejected.

### Workarounds

Ensure the the name of the Chart does not comprise/contain POSIX pathname special directory references ie. dot-dot ("..") or dot ("."). In addition, ensuring that the `pull --untar` flag (or equivalent SDK option) refers to a unique/empty output directory prevents chart extraction from inadvertently overwriting existing files within the specified directory.

### Credits

Oleh Konko @1seal

Most recent entries from all

CVE-2026-29181 — OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)

GHSA-hr2v-4r36-88hr — Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment