{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-59323", "assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "state": "PUBLISHED", "assignerShortName": "vmware", "dateReserved": "2026-07-04T18:14:10.167Z", "datePublished": "2026-08-21T10:01:05.831Z", "dateUpdated": "2026-08-21T12:04:06.081Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "shortName": "vmware", "dateUpdated": "2026-08-21T10:01:05.831Z"}, "title": "Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability", "datePublic": "2026-08-20T09:55:00.000Z", "affected": [{"vendor": "VMware", "product": "Spring", "packageName": "Micrometer Tracing", "versions": [{"status": "affected", "version": "1.7.0 - 1.7.0", "lessThan": "1.7.0.1", "versionType": "Enterprise Support Only"}, {"status": "affected", "version": "1.7.0 - 1.7.0", "lessThan": "1.7.1", "versionType": "OSS"}, {"status": "affected", "version": "1.6.0 - 1.6.6", "lessThan": "1.6.6.1", "versionType": "enterprise support only"}, {"status": "affected", "version": "1.6.0 - 1.6.6", "lessThan": "1.6.7", "versionType": "oss"}, {"status": "affected", "version": "1.5.0 - 1.5.12", "lessThan": "1.5.13", "versionType": "enterprise support only"}, {"status": "affected", "version": "1.4.13 and earlier", "lessThan": "1.4.14", "versionType": "enterprise support only"}], "defaultStatus": "affected"}], "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\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.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<p>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&nbsp;<code>baggage</code>&nbsp;headers.</p><p>Specifically, an application is vulnerable when all the following are true:</p><ul><li>The application uses a vulnerable version of&nbsp;<code>io.micrometer:micrometer-tracing-bridge-brave</code>.</li><li>W3C propagation is active (either configured manually or active by default, such as in Spring Boot 3.x+).</li><li>Baggage propagation is enabled (which is the default in Spring Boot 3.x+) and a baggage manager (such as&nbsp;<code>BraveBaggageManager</code>) is configured to handle baggage fields.</li><li>The application processes requests or messages from untrusted sources with&nbsp;<code>baggage</code>&nbsp;headers which it normally should not, see:&nbsp;<a href=\"https://www.w3.org/TR/trace-context/#security-considerations\">https://www.w3.org/TR/trace-context/#security-considerations</a>.</li><li>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.</li></ul><p>The last two points are very important: normally this should not affect applications because they should not receive untrusted and unlimited input for baggage.</p><ul><li>The application processes requests or messages from untrusted sources with&nbsp;<code>baggage</code>&nbsp;headers.</li></ul><p>When extracting baggage from the W3C&nbsp;<code>baggage</code>&nbsp;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&nbsp;<code>baggage</code>&nbsp;headers containing many key-value pairs, causing unconditional&nbsp;<code>BaggageField</code>&nbsp;allocations per entry. This leads to garbage collection pressure, high CPU usage, and potential application crash via&nbsp;<code>OutOfMemoryError</code>.</p>"}]}], "references": [{"url": "https://spring.io/security/cve-2026-59323"}], "metrics": [{"format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}], "cvssV3_1": {"version": "3.1", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "NONE", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "availabilityImpact": "LOW", "baseSeverity": "MEDIUM", "baseScore": 5.3, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"}}], "source": {"discovery": "UNKNOWN"}, "x_generator": {"engine": "Vulnogram 1.0.4"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-08-21T12:03:29.254669Z", "id": "CVE-2026-59323", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-08-21T12:04:06.081Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-59323", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-21T12:03:29.254669Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-08-21T12:03:45.230Z"}}], "cna": {"title": "Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability", "source": {"discovery": "UNKNOWN"}, "metrics": [{"format": "CVSS", "cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "affected": [{"vendor": "VMware", "product": "Spring", "versions": [{"status": "affected", "version": "1.7.0 - 1.7.0", "lessThan": "1.7.0.1", "versionType": "Enterprise Support Only"}, {"status": "affected", "version": "1.7.0 - 1.7.0", "lessThan": "1.7.1", "versionType": "OSS"}, {"status": "affected", "version": "1.6.0 - 1.6.6", "lessThan": "1.6.6.1", "versionType": "enterprise support only"}, {"status": "affected", "version": "1.6.0 - 1.6.6", "lessThan": "1.6.7", "versionType": "oss"}, {"status": "affected", "version": "1.5.0 - 1.5.12", "lessThan": "1.5.13", "versionType": "enterprise support only"}, {"status": "affected", "version": "1.4.13 and earlier", "lessThan": "1.4.14", "versionType": "enterprise support only"}], "packageName": "Micrometer Tracing", "defaultStatus": "affected"}], "datePublic": "2026-08-20T09:55:00.000Z", "references": [{"url": "https://spring.io/security/cve-2026-59323"}], "x_generator": {"engine": "Vulnogram 1.0.4"}, "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\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.", "supportingMedia": [{"type": "text/html", "value": "<p>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&nbsp;<code>baggage</code>&nbsp;headers.</p><p>Specifically, an application is vulnerable when all the following are true:</p><ul><li>The application uses a vulnerable version of&nbsp;<code>io.micrometer:micrometer-tracing-bridge-brave</code>.</li><li>W3C propagation is active (either configured manually or active by default, such as in Spring Boot 3.x+).</li><li>Baggage propagation is enabled (which is the default in Spring Boot 3.x+) and a baggage manager (such as&nbsp;<code>BraveBaggageManager</code>) is configured to handle baggage fields.</li><li>The application processes requests or messages from untrusted sources with&nbsp;<code>baggage</code>&nbsp;headers which it normally should not, see:&nbsp;<a href=\"https://www.w3.org/TR/trace-context/#security-considerations\">https://www.w3.org/TR/trace-context/#security-considerations</a>.</li><li>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.</li></ul><p>The last two points are very important: normally this should not affect applications because they should not receive untrusted and unlimited input for baggage.</p><ul><li>The application processes requests or messages from untrusted sources with&nbsp;<code>baggage</code>&nbsp;headers.</li></ul><p>When extracting baggage from the W3C&nbsp;<code>baggage</code>&nbsp;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&nbsp;<code>baggage</code>&nbsp;headers containing many key-value pairs, causing unconditional&nbsp;<code>BaggageField</code>&nbsp;allocations per entry. This leads to garbage collection pressure, high CPU usage, and potential application crash via&nbsp;<code>OutOfMemoryError</code>.</p>", "base64": false}]}], "providerMetadata": {"orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "shortName": "vmware", "dateUpdated": "2026-08-21T10:01:05.831Z"}}}, "cveMetadata": {"cveId": "CVE-2026-59323", "state": "PUBLISHED", "dateUpdated": "2026-08-21T12:04:06.081Z", "dateReserved": "2026-07-04T18:14:10.167Z", "assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "datePublished": "2026-08-21T10:01:05.831Z", "assignerShortName": "vmware"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"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"}]}], "source": "[email protected]"}], "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\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": "CVE-2026-59323", "lastModified": "2026-08-21T12:16:30.510", "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": "[email protected]", "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": "[email protected]", "url": "https://spring.io/security/cve-2026-59323"}], "sourceIdentifier": "[email protected]", "vulnStatus": "Received"}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1.7.0,1.7.0.1)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1.7.0,1.7.1)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1.6.0,1.6.6.1)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1.6.0,1.6.7)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1.5.0,1.5.13)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[1.4.13,1.4.14)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "Spring", "source": "cna", "vendor": "VMware"}, "product": "spring", "vendor": "vmware"}], "created": "2026-08-21T11:30:03.873902+00:00", "updated": "2026-08-21T11:30:04.178668+00:00", "vendors": ["vmware", "vmware$PRODUCT$spring"], "weaknesses": ["CWE-749"]}