FKIE_CVE-2026-59323

Vulnerability from fkie_nvd - Published: 2026-08-21 10:16 - Updated: 2026-10-16 15:10
Severity
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Summary
An application using Micrometer Tracing with W3C baggage propagation in the Brave bridge is vulnerable to denial of service (DoS) due to unbounded object allocation when extracting incoming baggage headers. Micrometer Tracing 1.7.0 Micrometer Tracing 1.6.0 - 1.6.6 Micrometer Tracing 1.5.0 - 1.5.12 Micrometer Tracing 1.4.13 and earlier
References
security@vmware.comhttps://spring.io/security/cve-2026-59323
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Micrometer Tracing",
          "vendor": "Spring",
          "versions": [
            {
              "status": "affected",
              "version": "1.7.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "1.6.6",
              "status": "affected",
              "version": "1.6.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "1.5.12",
              "status": "affected",
              "version": "1.5.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "1.4.13",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "security@vmware.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "An application using Micrometer Tracing with W3C baggage propagation in the Brave bridge is vulnerable to denial of service (DoS) due to unbounded object allocation when extracting incoming baggage headers.\nMicrometer Tracing 1.7.0\nMicrometer Tracing 1.6.0 - 1.6.6\nMicrometer Tracing 1.5.0 - 1.5.12\nMicrometer Tracing 1.4.13 and earlier"
    },
    {
      "lang": "es",
      "value": "Una aplicaci\u00f3n que utiliza Micrometer Tracing con propagaci\u00f3n de baggage W3C en el puente Brave es vulnerable a denegaci\u00f3n de servicio (DoS) debido a la asignaci\u00f3n ilimitada de objetos al extraer los encabezados de baggage entrantes.\n\nEspec\u00edficamente, una aplicaci\u00f3n es vulnerable cuando se cumplen todas las siguientes condiciones:\n\n  *  La aplicaci\u00f3n utiliza una versi\u00f3n vulnerable de io.micrometer:micrometer-tracing-bridge-brave.\n  *  La propagaci\u00f3n W3C est\u00e1 activa (ya sea configurada manualmente o activa por defecto, como en Spring Boot 3.x+).\n  *  La propagaci\u00f3n de baggage est\u00e1 habilitada (lo cual es el valor por defecto en Spring Boot 3.x+) y un gestor de baggage (como BraveBaggageManager) est\u00e1 configurado para manejar los campos de baggage.\n  *  La aplicaci\u00f3n procesa solicitudes o mensajes de fuentes no confiables con encabezados de baggage que normalmente no deber\u00eda, ver: https://www.w3.org/TR/trace-context/#security-considerations .\n  *  Los componentes de red, incluido el servidor (HTTP) que recibe la solicitud, no limitan el tama\u00f1o del encabezado o el l\u00edmite es lo suficientemente alto como para causar problemas.\n\nLos dos \u00faltimos puntos son muy importantes: normalmente esto no deber\u00eda afectar a las aplicaciones porque no deber\u00edan recibir entrada no confiable e ilimitada para baggage.\n\n  *  La aplicaci\u00f3n procesa solicitudes o mensajes de fuentes no confiables con encabezados de baggage.\n\nAl extraer baggage del encabezado de baggage W3C, las entradas entrantes se analizan sin aplicar l\u00edmites en el n\u00famero de entradas o el tama\u00f1o del encabezado seg\u00fan lo exigido por la especificaci\u00f3n W3C Baggage. Un atacante puede enviar solicitudes o mensajes con encabezados de baggage inflados artificialmente que contienen muchos pares clave-valor, causando asignaciones incondicionales de BaggageField por entrada. Esto conduce a presi\u00f3n en la recolecci\u00f3n de basura, alto uso de CPU y un posible fallo de la aplicaci\u00f3n a trav\u00e9s de OutOfMemoryError."
    }
  ],
  "id": "CVE-2026-59323",
  "lastModified": "2026-10-16T15:10:00.103",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "security@vmware.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-59323",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-08-21T12:03:29.254669Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-08-21T10:16:38.910",
  "references": [
    {
      "source": "security@vmware.com",
      "url": "https://spring.io/security/cve-2026-59323"
    }
  ],
  "sourceIdentifier": "security@vmware.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-770"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.