fix(deps): bump go.opentelemetry.io/otel to v1.44.0 for GO-2026-5158 - #363
fix(deps): bump go.opentelemetry.io/otel to v1.44.0 for GO-2026-5158#363bomly-guy wants to merge 1 commit into
Conversation
Resolves the baggage header-length advisory (GO-2026-5158 / CVE-2026-41178 / GHSA-5wrp-cwcj-q835) by moving otel, otel/metric, and otel/trace from the affected v1.43.0 to the fixed v1.44.0. govulncheck confirms no vulnerable symbols were reachable before the bump. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request updates three indirect OpenTelemetry modules in ChangesOpenTelemetry dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bomly Diff SummaryCompared Overview
Dependency ChangesSummary: 0 added, 3 version changed, 0 detail changes, 0 removed. Changed Dependencies
VulnerabilitiesSummary: 0 introduced, 0 persisted, 1 resolved. Resolved Vulnerabilities
License Changes✅ No license changes. Project Posture✅ No project posture changes ( Policy Findings✅ No policy differences were identified. |
Summary
Triage of two OSV advisories detected 2026-07-31 by scanning a bomly-generated SBOM of this repo.
GO-2026-5158 / CVE-2026-41178 / GHSA-5wrp-cwcj-q835 — otel baggage parsing (fixed here)
go.opentelemetry.io/otelv1.43.0, which sits in the affected range ([1.41.0, 1.42.0)and[1.43.0, 1.44.0)). It is an indirect dependency, pulled in byanchore/syft v1.49.0,anchore/grype v0.116.0,containerd/v2, and the GCP/OTel contrib chain.otel/baggage,otel/propagation) are in our build graph, butgovulncheck ./...symbol analysis reports no vulnerable symbols reachable (baggage.New/Parse,Baggage.Extractare never called from our code paths).otel,otel/metric,otel/trace);otel/sdkis not named in the advisory and stays at v1.43.0. After the bump govulncheck reports zero package-level findings.GO-2026-5932 — golang.org/x/crypto/openpgp (documented as unreachable; no code change)
golang.org/x/crypto/openpgpis not imported anywhere in our dependency closure —go list -deps ./...shows only ProtonMail's maintained forkgithub.com/ProtonMail/go-crypto/openpgp(used by syft). govulncheck reports this advisory at module level only ("vulnerability in modules you require, but your code doesn't appear to call these").x/cryptomodule itself is legitimately required by syft/stereoscope and by us for other packages.fail-on: highand this advisory carries no severity, so it does not block CI. Disposition: accepted / unreachable at package level; re-evaluate only if a future dependency starts importingx/crypto/openpgp.Verification
make test— full suite green.govulncheck ./...after the bump: "Your code is affected by 0 vulnerabilities … 0 vulnerabilities in packages you import"; only the unfixable module-level GO-2026-5932 notice remains.go build ./...clean.🤖 Generated with Claude Code
Summary by CodeRabbit