CVE-2026-128086: 
Grafana Analyse et atténuation de la vulnérabilité

Aperçu

CVE-2026-128086 is a memory-allocation amplification vulnerability in OpenTelemetry-Go (opentelemetry-go) caused by eager materialization of W3C baggage properties during parsing. It affects go.opentelemetry.io/otel/baggage and go.opentelemetry.io/otel/propagation from version 1.0.0-RC1 through versions prior to 1.47.0. The vulnerability was privately reported, published to the GitHub Advisory Database on November 13, 2026, and assigned GHSA-RRFC-GJM9-CGRJ. It carries a CVSS v3.1 base score of 5.3 (Medium) (Github Advisory, Feedly).

Détails techniques

The root cause (CWE-400, CWE-405, CWE-770) lies in the parseMember function within go.opentelemetry.io/otel/baggage, which eagerly converts every W3C baggage property into a Go Property struct, grows property slices, serializes members, and copies properties into internal/baggage.Item — all during the initial parse call. A valid 8,191-byte baggage header containing one member and 4,094 short properties (e.g., "k=v" + strings.Repeat(";a", 4094)) causes approximately 778 KB of cumulative allocation per parse call, representing roughly 95× amplification relative to input size. The retained live heap per parsed result is approximately 164 KB (~20× input). Exploitation requires: baggage extraction to be explicitly enabled, attacker-controlled HTTP headers to reach the parser, and extraction to occur before authentication or on a public route — a common pattern when otelhttp.NewHandler wraps the authentication middleware (Github Advisory, Security Advisory).

Impact

Successful exploitation degrades service availability through increased memory allocation traffic and garbage collection pressure. While the evidence does not establish reliable out-of-memory conditions or process termination, sustained or concurrent crafted requests can meaningfully increase GC overhead and reduce throughput on affected services. There is no confidentiality or integrity impact; the vulnerability is limited to availability (low) per the CVSS assessment. Services exposing baggage extraction on public or pre-authentication routes are most at risk (Github Advisory).

Exploitabilité

No public proof-of-concept exploit code exists, and there is no evidence of in-the-wild exploitation as of the advisory publication date (Feedly). 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 no authentication and no user interaction, but does require the target service to have baggage propagation explicitly enabled and extraction occurring before authentication — conditions that are not universally present (Github Advisory).

Étapes d’exploitation

  1. Reconnaissance: Identify services using OpenTelemetry-Go versions >= 1.0.0-RC1 and < 1.47.0 with baggage propagation enabled (e.g., via otelhttp.NewHandler wrapping public routes or routes where extraction precedes authentication).
  2. Craft malicious baggage header: Construct a valid W3C baggage header at or near the 8,192-byte limit with a single member and maximum properties, e.g., baggage: k=v;a;a;a;... (repeating ;a 4,094 times to reach 8,191 bytes).
  3. Send HTTP requests: Transmit HTTP requests containing the crafted baggage header to the target service's public or pre-authentication endpoints. Ensure the transport and any proxies accept the large header size.
  4. Amplify allocation pressure: Send concurrent or sustained requests to multiply the per-parse allocation (~778 KB per request) and increase garbage collection frequency, degrading service performance over time (Github Advisory, Security Advisory).

Indicateurs de compromis

  • Network: High volumes of HTTP requests containing large baggage headers (approaching 8 KB) targeting public or pre-authentication endpoints; repeated requests from the same source IP with near-maximum-size baggage headers.
  • Logs: Application logs showing elevated GC pause times or memory allocation warnings; access logs with requests carrying unusually large baggage header values on instrumented routes.
  • Process: Elevated Go runtime GC metrics (e.g., go_gc_duration_seconds, go_memstats_alloc_bytes) visible in Prometheus/OpenTelemetry metrics exports; increased heap allocation rates correlated with specific request patterns.

Atténuation et solutions de contournement

The primary remediation is to upgrade go.opentelemetry.io/otel/baggage and go.opentelemetry.io/otel/propagation to version 1.47.0, which validates and normalizes W3C property metadata in place during Parse and materializes Property structs lazily only when Member.Properties() is explicitly called (v1.47.0 Release, Fix Commit). If upgrading immediately is not possible, consider: (1) disabling baggage propagation entirely if not required; (2) ensuring authentication middleware executes before otelhttp.NewHandler so unauthenticated requests never reach baggage extraction; (3) restricting baggage propagation to authenticated routes only; or (4) implementing rate limiting or header-size restrictions at the proxy/load balancer layer to limit the rate of large baggage header requests (Github Advisory).

Réactions de la communauté

The advisory was authored by maintainer pellared and analyzed by XSAM, with alex131125 credited as the reporter (Github Advisory). Red Hat tracked the issue via Bugzilla (bug 2573410) and published a security advisory, indicating downstream ecosystem awareness. No significant broader media coverage or notable community debate has been identified beyond standard vulnerability database aggregation.

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 Grafana Vulnérabilités :

CVE ID

Gravité

Partition

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2026-128086MEDIUM5.3
  • Grafana logoGrafana
  • container-tools:rhel8::containers-common
NonOuiNov 13, 2026
CVE-2026-128085MEDIUM5.3
  • cAdvisor logocAdvisor
  • crossplane-provider-aws-datapipeline
NonOuiNov 13, 2026
CVE-2026-126358MEDIUM5.3
  • JavaScript logoJavaScript
  • wazuh-dashboard-fips
NonOuiNov 13, 2026
CVE-2026-126357MEDIUM5.3
  • JavaScript logoJavaScript
  • claude-agent-acp
NonOuiNov 13, 2026
CVE-2026-126359LOW3.4
  • JavaScript logoJavaScript
  • hono
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