cve.bz

CVE-2026-81869 open-telemetry opentelemetry-go: Improper Handling of Unicode Encoding

5.1 mediumEPSS 0.2%Fix available

Medium (5.1) in open-telemetry opentelemetry-go. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in go.opentelemetry.io/otel/sdk 1.33.0.

On this page
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.10.0 until 1.33.0, the sdk/trace/span.go attribute truncation path can fail to enforce AttributeValueLengthLimit for string and string-slice attributes containing the valid Unicode replacement character U+FFFD. safeTruncateValidUTF8 treats the valid replacement rune as invalid UTF-8 and returns the original input, while strings.ToValidUTF8 leaves that valid rune unchanged, so a second safeTruncate attempt can also return the oversized value. An attacker who controls span attribute content can retain values longer than the configured limit, increasing per-span memory use and weakening denial-of-service protection in the instrumented process. This issue is fixed in version 1.33.0.

Severity

CVSS 4.0

5.1 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-176 Improper Handling of Unicode Encoding
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-81869 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-81869?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-81869?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-81869 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
open-telemetry opentelemetry-go>= 1.10.0, < 1.33.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p9f8-wvj8-2fg8Gogo.opentelemetry.io/otel/sdk>=1.10.0 <1.33.01.33.0
GO-2026-6616Gogo.opentelemetry.io/otel/sdk>=1.10.0 <1.33.01.33.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13golang-opentelemetry-otelno fix listedDEBIAN-CVE-2026-81869
Debian14golang-opentelemetry-otel1.43.0-1DEBIAN-CVE-2026-81869
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 1 moregolang-opentelemetry-otelno fix listedUBUNTU-CVE-2026-81869
Azure Linux3cert-manager1.12.15-14AZL-103143
Azure Linux3cloud-provider-kubevirtno fix listedAZL-103131
Azure Linux3cri-ono fix listedAZL-103073
Azure Linux3cri-toolsno fix listedAZL-103149
Azure Linux3docker-buildxno fix listedAZL-103155
Azure Linux3docker-compose2.27.0-15AZL-103161
Azure Linux3flannel0.24.2-33AZL-103170
Azure Linux3kata-containers-ccno fix listedAZL-103179
Azure Linux3kedano fix listedAZL-103191
Azure Linux3kube-vip-cloud-provider0.0.10-10AZL-103233
Azure Linux3kubernetesno fix listedAZL-103221
Azure Linux3moby-containerd-cc1.7.7-18AZL-103239
3 more for Azure Linux in the JSON.

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON