CVE-2026-128085: 
cAdvisor Analyse et atténuation de la vulnérabilité

Aperçu

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).

Détails techniques

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).

Exploitabilité

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.

Étapes d’exploitation

  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).

Indicateurs de compromis

  • 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.

Atténuation et solutions de contournement

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.

Ressources supplémentaires

État de correction de la distribution Linux

Corrigez la disponibilité entre les grandes distributions Linux et leurs versions.

Debian

Affecté

bookworm

golang-opentelemetry-otel

Affecté

sid

golang-opentelemetry-otel

Affecté

trixie

golang-opentelemetry-otel

Affecté

Ubuntu

Inconnu

devel

golang-opentelemetry-otel

Inconnu

jammy

golang-opentelemetry-otel

Inconnu

jammy (esm-apps)

golang-opentelemetry-otel

Inconnu

noble

golang-opentelemetry-otel

Inconnu

noble (esm-apps)

golang-opentelemetry-otel

Inconnu

resolute

golang-opentelemetry-otel

Inconnu

resolute (esm-apps)

golang-opentelemetry-otel

Inconnu

RHEL / CentOS

Affecté

OpenShift

conmon-rs.src

Affecté

RHEL 8

Non affecté

RHEL 9

Non affecté

RHEL 10

Non affecté

Source: Ce rapport a été généré à l’aide de l’IA

Connexe cAdvisor Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-116591HIGH8.7
  • cAdvisor logocAdvisor
  • knative-serving-fips-1.23
NonOuiOct 26, 2026
CVE-2026-97032HIGH7.5
  • Go logoGo
  • grafana-pyroscope-fips-2.2
NonOuiOct 08, 2026
CVE-2026-97031HIGH7.5
  • Go logoGo
  • argo-workflows-4.1
NonOuiOct 08, 2026
CVE-2026-85747MEDIUM6.8
  • cAdvisor logocAdvisor
  • fluxcd-source-controller-fips
NonOuiOct 13, 2026
CVE-2026-128085MEDIUM5.3
  • cAdvisor logocAdvisor
  • crossplane-provider-aws-imagebuilder-fips
NonOuiNov 13, 2026

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.

Évaluation de la demande

Ressources Wiz supplémentaires

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités