https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T21:46:07.528582+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2026-29181 CVE-2026-29181 — OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification) 2026-10-03T21:46:07.930491+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-389r-gv7p-r3rp GHSA-389r-gv7p-r3rp — go-git's improper parsing of specially crafted objects may lead to inconsistent interpretation compared to upstream Git 2026-10-03T21:46:07.930587+00:00

Affected: Go: github.com/go-git/go-git/v6, Go: github.com/go-git/go-git/v5

### Impact `go-git` may parse malformed Git objects in a way that differs from upstream Git. When `commit` or `tag` objects contain ambiguous or malformed headers, `go-git`’s decoded representation may expose values differently from how Git itself would interpret or reject the same object.

Additionally, `go-git`’s commit signing and verification logic operates over commit data reconstructed from `go-git`’s parsed representation rather than the original raw object bytes. As a result, `go-git` may sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository.

This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed.

### Patches Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to v5 are likely to be affected, users are recommended to upgrade to a supported `go-git` version.

### Credit

Thanks to @bugbunny-research (https://bugbunny.ai/) for reporting this to `sigstore/gitsign`, and to @wlynch, @patzielinski and @adityasaky for coordinating the disclosure with the `go-git` project. :bow: :1st_place_medal:

Thanks to @wayphinder for reporting this to the `go-git` project. :bow: