Vulnerability-Lookup

CVE-2026-59323 (GCVE-0-2026-59323)

Vulnerability from cvelistv5 – Published: 2026-08-21 10:01 – Updated: 2026-08-27 18:04

Title

Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability

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

Severity

5.3 (Medium)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

SSVC

Exploitation: none Automatable: yes Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2026-08-21 12:03 UTC

CWE

CWE-770 Allocation of Resources Without Limits or Throttling
CWE-770 - Allocation of Resources Without Limits or Throttling

Assigner

vmware CNA under the mitre root

CNA scorecard C 64/100 over 247 records in the last 180 days details

References

1 reference

URL	Tags
https://spring.io/security/cve-2026-59323

Impacted products

1 product

Vendor	Product	Version	CPE status
Spring	Micrometer Tracing	Affected: 1.7.0 (custom) Affected: 1.6.0 , ≤ 1.6.6 (custom) Affected: 1.5.0 , ≤ 1.5.12 (custom) Affected: 0 , ≤ 1.4.13 (custom)	guessed

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-59323",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-21T12:03:29.254669Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-770",
                "description": "CWE-770 Allocation of Resources Without Limits or Throttling",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-08-21T16:44:48.719Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "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"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eAn 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.\u003c/p\u003e\u003cp\u003eMicrometer Tracing 1.7.0\u003cbr/\u003eMicrometer Tracing 1.6.0 - 1.6.6\u003cbr/\u003eMicrometer Tracing 1.5.0 - 1.5.12\u003cbr/\u003eMicrometer Tracing 1.4.13 and earlier\u003c/p\u003e"
            }
          ],
          "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"
        }
      ],
      "impacts": [
        {
          "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."
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "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"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "CWE-770 Allocation of Resources Without Limits or Throttling",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-27T18:04:50.627Z",
        "orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d",
        "shortName": "vmware"
      },
      "references": [
        {
          "url": "https://spring.io/security/cve-2026-59323"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d",
    "assignerShortName": "vmware",
    "cveId": "CVE-2026-59323",
    "datePublished": "2026-08-21T10:01:05.831Z",
    "dateReserved": "2026-07-04T18:14:10.167Z",
    "dateUpdated": "2026-08-27T18:04:50.627Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-59323",
      "date": "2026-10-20",
      "epss": "0.00402",
      "percentile": "0.33062"
    },
    "nvd": {
      "cve": {
        "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"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Important",
      "current_release_date": "2026-10-05T09:04:16+00:00",
      "cve": "CVE-2026-59323",
      "id": "CVE-2026-59323",
      "initial_release_date": "2026-08-21T10:01:05.831000+00:00",
      "product_status:known_affected": "2",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "io.micrometer/micrometer-tracing-bridge-brave: Micrometer Tracing Brave Bridge: Denial of Service via W3C Baggage Propagation",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-59323.json",
      "version": "3"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-59323",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-21T12:03:29.254669Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "problemTypes": [
              {
                "descriptions": [
                  {
                    "cweId": "CWE-770",
                    "description": "CWE-770 Allocation of Resources Without Limits or Throttling",
                    "lang": "en",
                    "type": "CWE"
                  }
                ]
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-21T12:03:45.230Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "affected",
              "packageName": "Micrometer Tracing",
              "product": "Spring",
              "vendor": "VMware",
              "versions": [
                {
                  "lessThan": "1.7.0.1",
                  "status": "affected",
                  "version": "1.7.0 - 1.7.0",
                  "versionType": "Enterprise Support Only"
                },
                {
                  "lessThan": "1.7.1",
                  "status": "affected",
                  "version": "1.7.0 - 1.7.0",
                  "versionType": "OSS"
                },
                {
                  "lessThan": "1.6.6.1",
                  "status": "affected",
                  "version": "1.6.0 - 1.6.6",
                  "versionType": "enterprise support only"
                },
                {
                  "lessThan": "1.6.7",
                  "status": "affected",
                  "version": "1.6.0 - 1.6.6",
                  "versionType": "oss"
                },
                {
                  "lessThan": "1.5.13",
                  "status": "affected",
                  "version": "1.5.0 - 1.5.12",
                  "versionType": "enterprise support only"
                },
                {
                  "lessThan": "1.4.14",
                  "status": "affected",
                  "version": "1.4.13 and earlier",
                  "versionType": "enterprise support only"
                }
              ]
            }
          ],
          "datePublic": "2026-08-20T09:55:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eAn 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\u0026nbsp;\u003ccode\u003ebaggage\u003c/code\u003e\u0026nbsp;headers.\u003c/p\u003e\u003cp\u003eSpecifically, an application is vulnerable when all the following are true:\u003c/p\u003e\u003cul\u003e\u003cli\u003eThe application uses a vulnerable version of\u0026nbsp;\u003ccode\u003eio.micrometer:micrometer-tracing-bridge-brave\u003c/code\u003e.\u003c/li\u003e\u003cli\u003eW3C propagation is active (either configured manually or active by default, such as in Spring Boot 3.x+).\u003c/li\u003e\u003cli\u003eBaggage propagation is enabled (which is the default in Spring Boot 3.x+) and a baggage manager (such as\u0026nbsp;\u003ccode\u003eBraveBaggageManager\u003c/code\u003e) is configured to handle baggage fields.\u003c/li\u003e\u003cli\u003eThe application processes requests or messages from untrusted sources with\u0026nbsp;\u003ccode\u003ebaggage\u003c/code\u003e\u0026nbsp;headers which it normally should not, see:\u0026nbsp;\u003ca href=\"https://www.w3.org/TR/trace-context/#security-considerations\"\u003ehttps://www.w3.org/TR/trace-context/#security-considerations\u003c/a\u003e.\u003c/li\u003e\u003cli\u003eNetwork components including the (HTTP) server that receives the request do not limit the header size or the limit is high enough to cause issues.\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eThe last two points are very important: normally this should not affect applications because they should not receive untrusted and unlimited input for baggage.\u003c/p\u003e\u003cul\u003e\u003cli\u003eThe application processes requests or messages from untrusted sources with\u0026nbsp;\u003ccode\u003ebaggage\u003c/code\u003e\u0026nbsp;headers.\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eWhen extracting baggage from the W3C\u0026nbsp;\u003ccode\u003ebaggage\u003c/code\u003e\u0026nbsp;header, incoming entries are parsed without enforcing limits on the number of entries or header size as mandated by the W3C Baggage specification. An attacker can send requests or messages with artificially inflated\u0026nbsp;\u003ccode\u003ebaggage\u003c/code\u003e\u0026nbsp;headers containing many key-value pairs, causing unconditional\u0026nbsp;\u003ccode\u003eBaggageField\u003c/code\u003e\u0026nbsp;allocations per entry. This leads to garbage collection pressure, high CPU usage, and potential application crash via\u0026nbsp;\u003ccode\u003eOutOfMemoryError\u003c/code\u003e.\u003c/p\u003e"
                }
              ],
              "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\u00a0baggage\u00a0headers.\n\n\n\nSpecifically, an application is vulnerable when all the following are true:\n\n  *  The application uses a vulnerable version of\u00a0io.micrometer:micrometer-tracing-bridge-brave.\n  *  W3C propagation is active (either configured manually or active by default, such as in Spring Boot 3.x+).\n  *  Baggage propagation is enabled (which is the default in Spring Boot 3.x+) and a baggage manager (such as\u00a0BraveBaggageManager) is configured to handle baggage fields.\n  *  The application processes requests or messages from untrusted sources with\u00a0baggage\u00a0headers which it normally should not, see:\u00a0 https://www.w3.org/TR/trace-context/#security-considerations .\n  *  Network components including the (HTTP) server that receives the request do not limit the header size or the limit is high enough to cause issues.\n\n\n\n\nThe last two points are very important: normally this should not affect applications because they should not receive untrusted and unlimited input for baggage.\n\n  *  The application processes requests or messages from untrusted sources with\u00a0baggage\u00a0headers.\n\n\n\n\nWhen extracting baggage from the W3C\u00a0baggage\u00a0header, incoming entries are parsed without enforcing limits on the number of entries or header size as mandated by the W3C Baggage specification. An attacker can send requests or messages with artificially inflated\u00a0baggage\u00a0headers containing many key-value pairs, causing unconditional\u00a0BaggageField\u00a0allocations per entry. This leads to garbage collection pressure, high CPU usage, and potential application crash via\u00a0OutOfMemoryError."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "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"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-21T10:01:05.831Z",
            "orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d",
            "shortName": "vmware"
          },
          "references": [
            {
              "url": "https://spring.io/security/cve-2026-59323"
            }
          ],
          "source": {
            "discovery": "UNKNOWN"
          },
          "title": "Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability",
          "x_generator": {
            "engine": "Vulnogram 1.0.4"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d",
        "assignerShortName": "vmware",
        "cveId": "CVE-2026-59323",
        "datePublished": "2026-08-21T10:01:05.831Z",
        "dateReserved": "2026-07-04T18:14:10.167Z",
        "dateUpdated": "2026-08-21T16:44:48.719Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}

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

References

	URL	Tags
	security@vmware.com	https://spring.io/security/cve-2026-59323

Impacted products

	Vendor	Product	Version

JSON

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"
    }
  ]
}

GHSA-RJ39-56XF-V987

Vulnerability from github – Published: 2026-08-21 12:30 – Updated: 2026-08-21 18:34

Details

Specifically, an application is vulnerable when all the following are true:

The application uses a vulnerable version of io.micrometer:micrometer-tracing-bridge-brave.
W3C propagation is active (either configured manually or active by default, such as in Spring Boot 3.x+).
Baggage propagation is enabled (which is the default in Spring Boot 3.x+) and a baggage manager (such as BraveBaggageManager) is configured to handle baggage fields.
The application processes requests or messages from untrusted sources with baggage headers which it normally should not, see: https://www.w3.org/TR/trace-context/#security-considerations .
Network components including the (HTTP) server that receives the request do not limit the header size or the limit is high enough to cause issues.

The last two points are very important: normally this should not affect applications because they should not receive untrusted and unlimited input for baggage.

The application processes requests or messages from untrusted sources with baggage headers.

When extracting baggage from the W3C baggage header, incoming entries are parsed without enforcing limits on the number of entries or header size as mandated by the W3C Baggage specification. An attacker can send requests or messages with artificially inflated baggage headers containing many key-value pairs, causing unconditional BaggageField allocations per entry. This leads to garbage collection pressure, high CPU usage, and potential application crash via OutOfMemoryError.

Severity

5.3 (Medium)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-59323"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-770"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-21T10:16:38Z",
    "severity": "MODERATE"
  },
  "details": "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\u00a0baggage\u00a0headers.\n\n\n\nSpecifically, an application is vulnerable when all the following are true:\n\n  *  The application uses a vulnerable version of\u00a0io.micrometer:micrometer-tracing-bridge-brave.\n  *  W3C propagation is active (either configured manually or active by default, such as in Spring Boot 3.x+).\n  *  Baggage propagation is enabled (which is the default in Spring Boot 3.x+) and a baggage manager (such as\u00a0BraveBaggageManager) is configured to handle baggage fields.\n  *  The application processes requests or messages from untrusted sources with\u00a0baggage\u00a0headers which it normally should not, see:\u00a0 https://www.w3.org/TR/trace-context/#security-considerations .\n  *  Network components including the (HTTP) server that receives the request do not limit the header size or the limit is high enough to cause issues.\n\n\n\n\nThe last two points are very important: normally this should not affect applications because they should not receive untrusted and unlimited input for baggage.\n\n  *  The application processes requests or messages from untrusted sources with\u00a0baggage\u00a0headers.\n\n\n\n\nWhen extracting baggage from the W3C\u00a0baggage\u00a0header, incoming entries are parsed without enforcing limits on the number of entries or header size as mandated by the W3C Baggage specification. An attacker can send requests or messages with artificially inflated\u00a0baggage\u00a0headers containing many key-value pairs, causing unconditional\u00a0BaggageField\u00a0allocations per entry. This leads to garbage collection pressure, high CPU usage, and potential application crash via\u00a0OutOfMemoryError.",
  "id": "GHSA-rj39-56xf-v987",
  "modified": "2026-08-21T18:34:56Z",
  "published": "2026-08-21T12:30:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59323"
    },
    {
      "type": "WEB",
      "url": "https://spring.io/security/cve-2026-59323"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ]
}

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

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted

CVE-2026-59323 (GCVE-0-2026-59323)

FKIE_CVE-2026-59323

GHSA-RJ39-56XF-V987

Tags

Sightings

Nomenclature

Vulnerability timeline

Related by attack behaviour