Is go.opentelemetry.io/otel/trace 1.45 vulnerable?

Go · 1 release from 1.45.0 to 1.45.0 · latest go.opentelemetry.io/otel/trace is 1.47.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. go.opentelemetry.io/otel/trace 1.45.0, the last 1.45 release, is affected by 1 known security advisory (1 medium), including CVE-2026-128085. Upgrade to 1.47.0 or later to fix all of them.

Upgrade with:go get go.opentelemetry.io/otel/trace@v1.47.0

Is your project on an affected go.opentelemetry.io/otel/trace?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting go.opentelemetry.io/otel/trace 1.45.0

  • MediumCVE-2026-128085GHSA-q7gw-24fr-5p6913 Nov 2026

    opentelemetry-go: AttributeValueLengthLimit is fully bypassed by attribute values composed of valid U+FFFD runes

    Affected
    >=1.35.0 <1.47.0
    Fixed in
    1.47.0

Which of your client projects are still on go.opentelemetry.io/otel/trace 1.45?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact go.opentelemetry.io/otel/trace version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other go.opentelemetry.io/otel/trace versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.