Is go.opentelemetry.io/otel/sdk/log 0.18 vulnerable?
Go · 1 release from 0.18.0 to 0.18.0 · latest go.opentelemetry.io/otel/sdk/log is 1.47.0 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. go.opentelemetry.io/otel/sdk/log 0.18.0, the last 0.18 release, is affected by 3 known security advisories (2 medium, 1 low), including CVE-2026-128085, CVE-2026-81872, CVE-2026-81872. Upgrade to 1.47.0 or later to fix all of them.
go get go.opentelemetry.io/otel/sdk/log@v1.47.0Is your project on an affected go.opentelemetry.io/otel/sdk/log?
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/sdk/log 0.18.0
opentelemetry-go: AttributeValueLengthLimit is fully bypassed by attribute values composed of valid U+FFFD runes
- Affected
- >=0.9.0 <1.47.0
- Fixed in
- 1.47.0
OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full in go.opentelemetry.io/otel/sdk/log
- Affected
- <0.21.0
- Fixed in
- 0.21.0
OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full
- Affected
- <0.21.0
- Fixed in
- 0.21.0
Which of your client projects are still on go.opentelemetry.io/otel/sdk/log 0.18?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact go.opentelemetry.io/otel/sdk/log version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other go.opentelemetry.io/otel/sdk/log versions
- go.opentelemetry.io/otel/sdk/log 0.21
- go.opentelemetry.io/otel/sdk/log 0.20
- go.opentelemetry.io/otel/sdk/log 0.19
- go.opentelemetry.io/otel/sdk/log 0.17
- go.opentelemetry.io/otel/sdk/log 0.16
- go.opentelemetry.io/otel/sdk/log 0.15
- go.opentelemetry.io/otel/sdk/log 1.47
- go.opentelemetry.io/otel/sdk/log 0.22
- All go.opentelemetry.io/otel/sdk/log advisories
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.