go.opentelemetry.io/otel/sdk · opentelemetry-go: AttributeValueLengthLimit is fully bypassed by attribute values composed of valid U+FFFD runes
Affects go.opentelemetry.io/otel/sdkSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.47.0 when convenient.
Data as of 13 Nov 2026, 20:19 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 1.47.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade go.opentelemetry.io/otel/sdk and go.opentelemetry.io/otel/sdk/log and go.opentelemetry.io/otel/trace to 1.47.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogo.opentelemetry.io/otel/sdk | Affected
| Fixed in
|
| Gogo.opentelemetry.io/otel/sdk/log | Affected
| Fixed in
|
| Gogo.opentelemetry.io/otel/trace | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available in OpenTelemetry Go SDK version 1.47.0. Users should upgrade to version 1.47.0 or later to remediate this issue. No other mitigation or workaround is indicated by the vendor advisory or technical details.
Description
A vulnerability in go.opentelemetry.io/otel/sdk allows the AttributeValueLengthLimit truncation to be bypassed by attribute values composed entirely of valid U+FFFD (REPLACEMENT CHARACTER) runes. This occurs because the truncation logic incorrectly skips counting these runes, allowing values to exceed the configured length limit. The issue affects versions starting from v1.33.0 up to but not including v1.47.0, including the auto-instrumentation tracer introduced in v1.35.0. The flaw is a regression introduced by a previous fix and is distinct from the original issue fixed before v1.33.0. A patch is available in version 1.47.0.
References
- github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-q7gw-24fr-5p69 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/commit/017b08c7f1018b619991aaf6b2299d4beb9da1d3 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/log/v1.47.0 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/v1.47.0 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/releases/tag/trace/v1.47.0 (opens in a new tab)