CVE-2026-133184 (GCVE-0-2026-133184)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:23 – Updated: 2026-11-19 20:07| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/0a60e142b | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-19 14:21 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/0a60e142b.patch
393b70d07120… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
0a60e142b048
|
fix: [security] A push target only picks from the events | 393b70d07120… |
Fix summary
The fix enforces three security controls in the push path: (1) an explicit check that the event's 'published' flag is set before the event is eligible for push, returning a descriptive error if it is not; (2) a guard that skips any event for which the pushing user's fetch returns empty, preventing transmission of inaccessible events as empty shells; and (3) validation of the remote server's event-selection reply so that only UUIDs present in the originally offered event list are accepted, discarding any identifiers the remote references that were not part of the push offer.
Patch summary
In app/Model/Event.php, a new early-return check is added at the top of uploadEventToServer() that rejects the push if $event['Event']['published'] is empty. In app/Model/Server.php, three changes are made: (a) in the push() loop, a 'continue' statement is added when fetchEvent() returns empty, skipping inaccessible events; (b) the lastpushedid fallback logic is corrected to preserve the existing value when both successes and fails are empty; (c) in getEventIdsForPush(), the remote's JSON reply is validated as an array, filtered to string values, and then cross-referenced against the UUIDs in the $request (offered events) array so that only UUIDs present in both sets are returned.
CVSS rationale
AV:N: The push occurs over the network between MISP instances. AC:L: Triggering a push is a standard user action with no special race or timing conditions. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with push permissions is required. UI:N: No additional user interaction beyond initiating the push. VC:L: Confidential event data (unpublished events, events the user cannot access) is disclosed to the remote server. VI:N, VA:N: No integrity or availability impact on the source. SC:N, SI:N, SA:N: The remote server receives data but its own confidentiality, integrity, and availability are not compromised.
Weakness rationale
- CWE-862 The push mechanism does not enforce that events are published or that the pushing user has read access before transmitting them to a remote server, constituting a missing authorization check on data egress.
- CWE-20 The remote server's reply selecting events to accept is used without validating that the referenced identifiers belong to the set of events actually offered in the push request, allowing out-of-scope references.
Attack pattern rationale
- CAPEC-126 The MISP push mechanism relies on a trusted relationship between the source and remote MISP instances. The source trusts the push flow and the remote's reply without enforcing proper authorization (published status, user access) or validating the remote's selection against the offered set. The closest CAPEC is Leverage Trusted Relationship because the vulnerability arises from insufficient validation within a trusted inter-system data exchange. Uncertainty: no CAPEC perfectly captures 'missing authorization on outbound data push'; CAPEC-126 is the best available match for a trusted-relationship data-flow flaw.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- PR:L assumes the attacker needs a standard authenticated user with push permissions; if push is restricted to administrators only, PR could be H.
- VC:L assumes the disclosed data (unpublished events, inaccessible event metadata) constitutes a low confidentiality impact; if the events contain highly sensitive threat intelligence, the impact could be higher.
- CAPEC-126 is the closest available mapping; no CAPEC precisely describes 'missing authorization on outbound data push in a trusted inter-system exchange.'
- The remote server's ability to reference non-offered events (CWE-20 component) is assessed as low impact because the events would still need to exist and be accessible on the source; the primary impact is the authorization bypass (CWE-862).
- The 'Co-Authored-By: Claude Opus 5.5' credit is included as listed in the commit metadata; its role as a remediation developer is inferred from the co-authorship line.
Model comparison
Selected qwen3.8:27b
by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.
| Model | Score | Agreement | Confidence | Assumptions |
|---|---|---|---|---|
qwen3.8:27b |
6 | 11 | medium | 6 |
- 2026-11-13 09:02 UTC Fix developed Corrective change authored (0a60e142b048513ef48a103ef15ae56e3b679e0e): fix: [security] A push target only picks from the events https://github.com/MISP/MISP/commit/0a60e142b.patch
- 2026-11-19 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/0a60e142b.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133184",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:06:48.582946Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T20:07:07.998Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"Event model (uploadEventToServer)",
"Server model (push, getEventIdsForPush)"
],
"product": "misp",
"programFiles": [
"app/Model/Event.php",
"app/Model/Server.php"
],
"repo": "https://github.com/MISP/MISP",
"vendor": "misp",
"versions": [
{
"lessThanOrEqual": "2.5.51",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.5.51",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization and input-validation flaw in its event push mechanism. When a user with push permissions initiates a push of events to a remote MISP instance, the system fails to enforce two critical checks: (1) it does not verify that an event is published before including it in the push, allowing unpublished (i.e., not yet publicly shared) events to be transmitted to the remote server; and (2) it does not verify that the pushing user has read access to the event, causing events the user cannot fetch to be sent as empty event shells, thereby disclosing the existence and metadata of events the user is not authorized to view. Additionally, the remote server\u0027s reply selecting which offered events to accept is used without validating that the selected identifiers actually correspond to events in the offered set, potentially allowing the remote to reference events outside the intended scope. The vulnerability requires an authenticated user with push permissions on the source MISP instance and a configured push target. The security impact is unauthorized disclosure of confidential threat-intelligence data (unpublished events and events restricted by user permissions) to a remote MISP instance that should not receive them."
}
],
"impacts": [
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Leverage Trusted Relationship"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:21:31Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-20",
"description": "CWE-20 Improper Input Validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:23:36.482Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/0a60e142b"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix enforces three security controls in the push path: (1) an explicit check that the event\u0027s \u0027published\u0027 flag is set before the event is eligible for push, returning a descriptive error if it is not; (2) a guard that skips any event for which the pushing user\u0027s fetch returns empty, preventing transmission of inaccessible events as empty shells; and (3) validation of the remote server\u0027s event-selection reply so that only UUIDs present in the originally offered event list are accepted, discarding any identifiers the remote references that were not part of the push offer."
}
],
"title": "MISP Push Mechanism Discloses Unpublished and Inaccessible Events to Remote Server",
"x_gcve": [
{
"extensions": {
"bcp-05-x-01": {
"ai_annotations": [
{
"ai_level": "generated",
"description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
"gna_source": 1,
"models": [
{
"gna_source": 1,
"identifier": "qwen3.8:27b",
"name": "qwen3.8:27b",
"source": "ollama"
}
],
"review_status": "full",
"scope": "record",
"tags": [
"ai-computer-assisted:llm-generated",
"ai-computer-assisted:classification"
]
}
]
},
"bcp-05-x-02": {
"x_patch2vuln": {
"assumptions": [
"The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.",
"PR:L assumes the attacker needs a standard authenticated user with push permissions; if push is restricted to administrators only, PR could be H.",
"VC:L assumes the disclosed data (unpublished events, inaccessible event metadata) constitutes a low confidentiality impact; if the events contain highly sensitive threat intelligence, the impact could be higher.",
"CAPEC-126 is the closest available mapping; no CAPEC precisely describes \u0027missing authorization on outbound data push in a trusted inter-system exchange.\u0027",
"The remote server\u0027s ability to reference non-offered events (CWE-20 component) is assessed as low impact because the events would still need to exist and be accessible on the source; the primary impact is the authorization bypass (CWE-862).",
"The \u0027Co-Authored-By: Claude Opus 5.5\u0027 credit is included as listed in the commit metadata; its role as a remediation developer is inferred from the co-authorship line."
],
"capecRationale": [
{
"capecId": "CAPEC-126",
"rationale": "The MISP push mechanism relies on a trusted relationship between the source and remote MISP instances. The source trusts the push flow and the remote\u0027s reply without enforcing proper authorization (published status, user access) or validating the remote\u0027s selection against the offered set. The closest CAPEC is Leverage Trusted Relationship because the vulnerability arises from insufficient validation within a trusted inter-system data exchange. Uncertainty: no CAPEC perfectly captures \u0027missing authorization on outbound data push\u0027; CAPEC-126 is the best available match for a trusted-relationship data-flow flaw."
}
],
"commit": "0a60e142b048513ef48a103ef15ae56e3b679e0e",
"confidence": "medium",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "ENISA"
},
{
"lang": "en",
"type": "remediation developer",
"value": "iglocska"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
}
],
"cvssRationale": "AV:N: The push occurs over the network between MISP instances. AC:L: Triggering a push is a standard user action with no special race or timing conditions. AT:N: No manipulation of the attack target is required. PR:L: An authenticated user with push permissions is required. UI:N: No additional user interaction beyond initiating the push. VC:L: Confidential event data (unpublished events, events the user cannot access) is disclosed to the remote server. VI:N, VA:N: No integrity or availability impact on the source. SC:N, SI:N, SA:N: The remote server receives data but its own confidentiality, integrity, and availability are not compromised.",
"draft": false,
"fixSummary": "The fix enforces three security controls in the push path: (1) an explicit check that the event\u0027s \u0027published\u0027 flag is set before the event is eligible for push, returning a descriptive error if it is not; (2) a guard that skips any event for which the pushing user\u0027s fetch returns empty, preventing transmission of inaccessible events as empty shells; and (3) validation of the remote server\u0027s event-selection reply so that only UUIDs present in the originally offered event list are accepted, discarding any identifiers the remote references that were not part of the push offer.",
"generatedAt": "2026-11-19T14:21:31.586210Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 6,
"confidence": "medium",
"model": "qwen3.8:27b",
"score": 6
}
],
"selectedModel": "qwen3.8:27b",
"selectionMethod": "deterministic-consensus-v1",
"selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
},
"patchSha256": "393b70d07120c4546bc6153eaa230f99a917884232801c0502a22fa869ce5b9b",
"patchSummary": "In app/Model/Event.php, a new early-return check is added at the top of uploadEventToServer() that rejects the push if $event[\u0027Event\u0027][\u0027published\u0027] is empty. In app/Model/Server.php, three changes are made: (a) in the push() loop, a \u0027continue\u0027 statement is added when fetchEvent() returns empty, skipping inaccessible events; (b) the lastpushedid fallback logic is corrected to preserve the existing value when both successes and fails are empty; (c) in getEventIdsForPush(), the remote\u0027s JSON reply is validated as an array, filtered to string values, and then cross-referenced against the UUIDs in the $request (offered events) array so that only UUIDs present in both sets are returned.",
"patchTruncated": false,
"patches": [
{
"commit": "0a60e142b048513ef48a103ef15ae56e3b679e0e",
"date": "Fri, 13 Nov 2026 10:02:39 +0100",
"patchSha256": "393b70d07120c4546bc6153eaa230f99a917884232801c0502a22fa869ce5b9b",
"retrievedAt": "2026-11-19T14:20:49.401797Z",
"source": "https://github.com/MISP/MISP/commit/0a60e142b.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/0a60e142b.patch",
"subject": "fix: [security] A push target only picks from the events"
}
],
"source": "https://github.com/MISP/MISP/commit/0a60e142b.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:21:31Z",
"version": "2.0.3"
},
"subject": "fix: [security] A push target only picks from the events",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The push mechanism does not enforce that events are published or that the pushing user has read access before transmitting them to a remote server, constituting a missing authorization check on data egress."
},
{
"cweId": "CWE-20",
"rationale": "The remote server\u0027s reply selecting events to accept is used without validating that the referenced identifiers belong to the set of events actually offered in the push request, allowing out-of-scope references."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (0a60e142b048513ef48a103ef15ae56e3b679e0e): fix: [security] A push target only picks from the events",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/0a60e142b.patch"
],
"timestamp": "2026-11-13T09:02:39Z",
"type": "fix-developed"
},
{
"description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
"id": "evt-fix-available-1",
"references": [
"https://github.com/MISP/MISP/commit/0a60e142b.patch"
],
"timestamp": "2026-11-19T14:20:49.401797Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20330"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133184",
"datePublished": "2026-11-19T14:23:36.482Z",
"dateReserved": "2026-11-19T14:23:32.867Z",
"dateUpdated": "2026-11-19T20:07:07.998Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"Event model (uploadEventToServer)",
"Server model (push, getEventIdsForPush)"
],
"product": "misp",
"programFiles": [
"app/Model/Event.php",
"app/Model/Server.php"
],
"repo": "https://github.com/MISP/MISP",
"vendor": "misp",
"versions": [
{
"lessThanOrEqual": "2.5.51",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "MISP contains an authorization and input-validation flaw in its event push mechanism. When a user with push permissions initiates a push of events to a remote MISP instance, the system fails to enforce two critical checks: (1) it does not verify that an event is published before including it in the push, allowing unpublished (i.e., not yet publicly shared) events to be transmitted to the remote server; and (2) it does not verify that the pushing user has read access to the event, causing events the user cannot fetch to be sent as empty event shells, thereby disclosing the existence and metadata of events the user is not authorized to view. Additionally, the remote server\u0027s reply selecting which offered events to accept is used without validating that the selected identifiers actually correspond to events in the offered set, potentially allowing the remote to reference events outside the intended scope. The vulnerability requires an authenticated user with push permissions on the source MISP instance and a configured push target. The security impact is unauthorized disclosure of confidential threat-intelligence data (unpublished events and events restricted by user permissions) to a remote MISP instance that should not receive them."
}
],
"id": "CVE-2026-133184",
"lastModified": "2026-11-19T20:17:49.233",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"ssvcData": {
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:21:31Z",
"version": "2.0.3"
}
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133184",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T20:06:48.582946Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-19T15:17:39.243",
"references": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"url": "https://github.com/MISP/MISP/commit/0a60e142b"
}
],
"sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-20"
},
{
"lang": "en",
"value": "CWE-862"
}
],
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"type": "Secondary"
}
]
}
}
}
}
Solutions
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.
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
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.