Repository navigation
Conversation
v1.41.0 fixes the multi-value baggage allocation issue but is affected by GO-2026-5158, so use the matching v1.42.0 module set and otelhttp v0.67.0. Co-authored-by: Derrick J. Wippler <thrawn01@gmail.com>
Tochemey
approved these changes
Nov 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes reachable vulnerability GO-2026-5506 (CVE-2026-29181, GHSA-mh2q-q3fh-2475) in
go.opentelemetry.io/otel. From v1.36.0 through v1.40.0, multi-valuebaggageheader extraction parses each field-value independently and aggregates members, so manybaggageheader lines can amplify CPU and allocations. The advisory fix is v1.41.0.v1.41.0 is itself affected by GO-2026-5158 (CVE-2026-41178), which drops the raw baggage length cap. This PR moves to v1.42.0, the first release at or above v1.41.0 that fixes GO-2026-5506 and is not affected by GO-2026-5158. Related modules are on the matching v1.42.0 / contrib v0.67.0 set.
go mod tidywas run. The Go version stays 1.26.10; v1.42.0 requires Go 1.25.0, so no toolchain bump was required.Versions
go.opentelemetry.io/otelgo.opentelemetry.io/otel/metricgo.opentelemetry.io/otel/sdkgo.opentelemetry.io/otel/tracego.opentelemetry.io/otel/sdk/metric(otelhttp test dep,go.sumonly)go.opentelemetry.io/contrib/instrumentation/net/http/otelhttpgo.opentelemetry.io/auto/sdk(indirect, required by otel v1.42.0)golang.org/x/sys(indirect, required by otel v1.42.0)github.com/cespare/xxhash/v2(indirect, required by otel v1.42.0)There are no OpenTelemetry exporter modules in this repository.
Verification
Go toolchain used: go1.26.10. govulncheck v1.9.0, vuln DB last modified 2026-10-27.
go build ./...— passedgo test ./...— passed (groupcache-go/v3,cluster,contrib,internal/lru,internal/singleflight,transport,transport/peer)govulncheck ./...— 0 reachable vulnerabilities. GO-2026-5506 and GO-2026-5158 are not reported.Unresolved
govulncheckstill reports 15 vulnerabilities ingolang.org/x/net v0.47.0(GO-2026-4918, GO-2026-5025, GO-2026-5026, GO-2026-5027, GO-2026-5028, GO-2026-5029, GO-2026-5030, GO-2026-5942, GO-2026-6603, GO-2026-6610, GO-2026-6611, GO-2026-6612, GO-2026-6617, GO-2026-6860, GO-2026-6866). They are module-level findings the scanner says this code does not call, andgolang.org/x/netwas already v0.47.0 before this change. Left unchanged so this PR stays limited to the OpenTelemetry fix.