VulnerabilityPublished 16 Sep 2026

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

Affects open-telemetry opentelemetry-goSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.33.0 when convenient.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.33.0

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 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 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade opentelemetry-go and github.com/open-telemetry/opentelemetry-go to 1.33.0.

Affected software

Product	Affected	Fixed in
open-telemetryopentelemetry-go	Affected >=1.10.0 <1.33.0	Fixed in 1.33.0
Gogithub.com/open-telemetry/opentelemetry-go`pkg:golang/github.com/open-telemetry/opentelemetry-go`Other threats	Affected >=1.10.0 <1.33.0	Fixed in 1.33.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should be aware of this limitation when enabling AttributeValueLengthLimit and consider additional monitoring or controls on attribute data. No vendor advisory or patch links are provided in the current data.

Description

CVE-2026-81869 is a medium severity vulnerability in the OpenTelemetry Go SDK trace package that allows bypass of the configured attribute value length limit for string attributes containing the Unicode replacement character U+FFFD. This flaw causes oversized attacker-controlled attribute values to be stored untruncated, weakening memory and denial-of-service protections. The vulnerability requires deployments with attribute value length limits enabled and attacker-controlled data recorded into span attributes. There is no indication of confidentiality or integrity impact.

Impact

Applications using the OpenTelemetry Go SDK with AttributeValueLengthLimit enabled can have their memory and denial-of-service protections weakened because oversized span attribute values containing U+FFFD are not truncated as intended. This allows attacker-controlled data to consume more memory per span than configured, potentially leading to increased resource consumption. There is no evidence of confidentiality or integrity compromise.

Summary

The OpenTelemetry Go SDK trace package fails to properly enforce the AttributeValueLengthLimit for string attributes containing the Unicode replacement character U+FFFD. The truncation function safeTruncate relies on safeTruncateValidUTF8, which treats any utf8.RuneError as invalid UTF-8 and returns the original input untruncated. However, Go's utf8.DecodeRuneInString returns utf8.RuneError for the valid U+FFFD rune, causing safeTruncateValidUTF8 to incorrectly treat it as invalid and skip truncation. The fallback to strings.ToValidUTF8 does not remove U+FFFD, so the attribute value remains oversized, bypassing configured memory limits. This issue was introduced in commit 49a6536 and affects versions >=1.10.0 and <1.33.0 of opentelemetry-go. The impact is increased memory usage and reduced denial-of-service protection in instrumented processes.

CWE-176Improper Handling of Unicode Encoding (opens in a new tab)
Variant weakness
The product does not properly handle when an input contains Unicode encoding.
Architecture and Design · Input Validation
Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
Input Validation (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.2 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Using Unicode Encoding to Bypass Validation Logic (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2026, 23:34 UTC

WeaknessesCWE-176, CWE-400

Technical details

References

Community reviews

Related threats