CVE-2026-59323 (GCVE-0-2026-59323)
Vulnerability from cvelistv5 – Published: 2026-08-21 10:01 – Updated: 2026-08-21 16:44
VLAI
EPSS
VEX
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.
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)
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
Assigner
References
1 reference
Impacted products
1 product
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| VMware | Spring |
Affected:
1.7.0 - 1.7.0 , < 1.7.0.1
(Enterprise Support Only)
Affected: 1.7.0 - 1.7.0 , < 1.7.1 (OSS) Affected: 1.6.0 - 1.6.6 , < 1.6.6.1 (enterprise support only) Affected: 1.6.0 - 1.6.6 , < 1.6.7 (oss) Affected: 1.5.0 - 1.5.12 , < 1.5.13 (enterprise support only) Affected: 1.4.13 and earlier , < 1.4.14 (enterprise support only) |
guessed |
Date Public
2026-08-20 09:55
{
"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": "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",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-59323",
"date": "2026-08-22",
"epss": "0.00372",
"percentile": "0.30558"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-59323\",\"sourceIdentifier\":\"security@vmware.com\",\"published\":\"2026-08-21T10:16:38.910\",\"lastModified\":\"2026-08-21T17:16:32.517\",\"vulnStatus\":\"Received\",\"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.\"}],\"affected\":[{\"source\":\"security@vmware.com\",\"affectedData\":[{\"vendor\":\"VMware\",\"product\":\"Spring\",\"defaultStatus\":\"affected\",\"packageName\":\"Micrometer Tracing\",\"versions\":[{\"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\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security@vmware.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L\",\"baseScore\":5.3,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-08-21T12:03:29.254669Z\",\"id\":\"CVE-2026-59323\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"yes\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-770\"}]}],\"references\":[{\"url\":\"https://spring.io/security/cve-2026-59323\",\"source\":\"security@vmware.com\"}]}}",
"vulnrichment": {
"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\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-770\", \"description\": \"CWE-770 Allocation of Resources Without Limits or Throttling\"}]}], \"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\": \"\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\", \"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-21T16:44:48.719Z\", \"dateReserved\": \"2026-07-04T18:14:10.167Z\", \"assignerOrgId\": \"dcf2e128-44bd-42ed-91e8-88f912c1401d\", \"datePublished\": \"2026-08-21T10:01:05.831Z\", \"assignerShortName\": \"vmware\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
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.
Loading…
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.
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.
Loading…
Loading…