Vulnerability DatabaseCVE-2026-128085

CVE-2026-128085: 
Terraform Community vulnerability analysis and mitigation

Overview

CVE-2026-128085 is a denial-of-service vulnerability in OpenTelemetry-Go (opentelemetry-go) caused by an incomplete fix for a prior advisory (GHSA-p9f8-wvj8-2fg8). The AttributeValueLengthLimit and WithAttributeValueLengthLimit truncation logic in sdk/internal/attrnorm, sdk/log/internal/attrnorm, and trace/auto.go fails to count valid U+FFFD (REPLACEMENT CHARACTER) runes, allowing attribute values composed of those characters to bypass configured memory bounds entirely. Affected versions span SDK v1.33.0–v1.46.x, SDK log v0.9.0–v1.46.x, and trace v1.35.0–v1.46.x; all are fixed in v1.47.0. It carries a CVSS v3.1 base score of 5.3 (Medium) (GitHub Advisory).

Technical details

The root cause is classified as CWE-135 (Incorrect Calculation of Multi-Byte String Length) and CWE-770 (Allocation of Resources Without Limits or Throttling). The shared truncate() helper (generated from internal/shared/attrnorm/truncate.go.tmpl) uses an "optimistic" fast path that iterates over the string with a range loop; when it encounters utf8.RuneError, it checks the decoded size to distinguish invalid bytes (size 1) from a legitimately encoded U+FFFD (size 3). Only the size-1 case diverts to the slow path — the size-3 U+FFFD case neither increments the character counter nor triggers truncation, so the rune is silently skipped. As a result, a 1,000-rune U+FFFD string (3,000 bytes) passes through completely untruncated even with a configured limit of 5 characters (15 bytes). The vulnerability is exploitable remotely without authentication, as span and log-record attributes are routinely derived from untrusted input such as HTTP headers or request bodies (GitHub Advisory, Fix Commit).

Impact

Successful exploitation allows an unauthenticated network attacker to inflate per-span and per-log-record memory retention linearly by injecting attribute values composed of U+FFFD runes, defeating the memory protection that operators explicitly configured via AttributeValueLengthLimit. Over time, this can exhaust memory and storage in observability pipelines (collectors, backends), degrading or denying service to the telemetry infrastructure. Confidentiality and integrity are not affected; the impact is limited to availability of the observability system (GitHub Advisory).

Exploitability

No public proof-of-concept exploit code has been published, and there is no evidence of in-the-wild exploitation at this time (GitHub Advisory). The EPSS score is 0.0, reflecting very low current exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires only network access and no authentication, but the impact is limited to denial of service against observability components rather than the instrumented application itself.

Exploitation steps

  1. Identify target: Locate a service instrumented with a vulnerable version of opentelemetry-go (SDK v1.33.0–v1.46.x or SDK log v0.9.0–v1.46.x) that has AttributeValueLengthLimit configured and exposes an endpoint that reflects attacker-controlled data into telemetry attributes (e.g., HTTP headers, query parameters, request body fields).
  2. Craft malicious payload: Construct a string composed entirely of valid U+FFFD (REPLACEMENT CHARACTER) runes — for example, 1,000 repetitions of \uFFFD (3,000 bytes). This value will bypass the truncation limit regardless of the configured character limit.
  3. Inject into telemetry attribute: Send HTTP requests (or other protocol messages) to the target service with the crafted payload in a field that gets recorded as a span or log-record attribute (e.g., a custom HTTP header, user-agent string, or request parameter that the application passes to span.SetAttributes() or record.AddAttributes()).
  4. Sustain the attack: Repeatedly send such requests to continuously accumulate oversized attributes in the span/log pipeline, inflating memory usage in the OpenTelemetry SDK, collector, and backend storage beyond operator-configured bounds.
  5. Achieve denial of service: Sustained memory pressure degrades or crashes the observability pipeline components, potentially causing loss of telemetry data and impacting monitoring/alerting capabilities (GitHub Advisory).

Indicators of compromise

  • Logs: Unusually large span or log-record attribute values (kilobytes or more) appearing in OpenTelemetry collector or backend logs, particularly attributes containing long sequences of the U+FFFD replacement character (UTF-8 encoding: 0xEF 0xBF 0xBD).
  • Memory/Resource: Abnormal memory growth in OpenTelemetry SDK processes, collectors, or telemetry backends correlated with incoming request volume; heap dumps showing large string allocations composed of repeated \uFFFD sequences.
  • Network: High-volume requests to instrumented service endpoints containing repeated \xEF\xBF\xBD byte sequences (U+FFFD in UTF-8) in headers, query strings, or body fields that are captured as telemetry attributes.

Mitigation and workarounds

Upgrade all affected OpenTelemetry-Go modules to version 1.47.0, which correctly counts valid U+FFFD runes toward the attribute value length limit: go.opentelemetry.io/otel/sdk v1.47.0, go.opentelemetry.io/otel/sdk/log v1.47.0, and go.opentelemetry.io/otel/trace v1.47.0 (SDK Release, SDK Log Release, Trace Release). As a short-term workaround prior to patching, implement input validation and rate limiting at the ingestion point to reject or truncate excessively large attribute values before they reach the SDK. Additionally, consider disabling AttributeValueLengthLimit enforcement reliance as a sole memory control and supplement with process-level memory limits on collector and backend components.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Affected

bookworm

golang-opentelemetry-otel

Affected

sid

golang-opentelemetry-otel

Affected

trixie

golang-opentelemetry-otel

Affected

RHEL / CentOS

Affected

OpenShift

conmon-rs.src

Affected

RHEL 8

Not Affected

RHEL 9

Not Affected

RHEL 10

Not Affected

Source: This report was generated using AI

Related Terraform Community vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-116591HIGH8.7
  • cAdvisor logocAdvisor
  • rancher-2.10
NoYesOct 26, 2026
CVE-2026-116587HIGH7.5
  • Docker logoDocker
  • gitlab-workhorse-ce-fips-19.5
NoYesOct 26, 2026
CVE-2026-97032HIGH7.5
  • Go logoGo
  • gitlab-kas-19.2
NoYesOct 08, 2026
CVE-2026-78669HIGH7.5
  • Go logoGo
  • cert-manager-google-cas-issuer
NoYesOct 08, 2026
CVE-2026-128085MEDIUM5.3
  • Terraform Community logoTerraform Community
  • crossplane-provider-aws-ecr
NoYesNov 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management