CVE-2026-133183 (GCVE-0-2026-133183)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:19 – Updated: 2026-11-19 14:44- CWE-862 - Missing Authorization
| URL | Tags |
|---|---|
| https://github.com/MISP/MISP/commit/389ce674c | 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:13 - Model
qwen3.8:27b- Input
-
https://github.com/MISP/MISP/commit/389ce674c.patch
74f3a4178ae1… - Confidence
- medium
| Commit | Subject | Patch SHA-256 |
|---|---|---|
389ce674c1f8
|
fix: [security] Pulls and feeds no longer update sharing | 74f3a4178ae1… |
Fix summary
The fix introduces a proper authorization check for remote capture operations. The captureRemote method now receives the full server context (or null for feeds) and stores both the internal flag and the remote organization identifier. A new __remoteMayUpdate method verifies that, for non-internal pulls, the remote organization is a member of the target sharing group (as owning org, in the SharingGroupOrg list, or via an all_orgs entry). For feeds (server is null), the update is always refused. When the check fails, the sharing group record is left unchanged while the pulled data still attaches to it, preserving data integrity without granting unauthorized metadata modification.
Patch summary
Three files are modified. In Feed.php, two calls to SharingGroup::captureRemote change the first argument from false to null, indicating a feed has no server context. In Server.php, the pull method now passes the full $server array instead of a derived boolean. In SharingGroup.php, the static $remoteCapture variable changes from a boolean to an associative array holding internal (bool) and remote_org_id (int|null). The captureRemote method signature changes from accepting a bool to accepting an array or null. A new private method __remoteMayUpdate is added, which returns true for internal links, and for non-internal links checks that remote_org_id is set, the group is not local, and the remote org matches the group's org_id, appears in SharingGroupOrg, or is covered by an all_orgs SharingGroupServer entry. In captureSGExisting, a guard clause is inserted before the existing update logic: if a remote capture is active and __remoteMayUpdate returns false, the method returns the existing group id without further
CVSS rationale
AV:N: MISP is a network-accessible web application; pulls and feeds are initiated over HTTP. AC:L: An attacker with a configured pull or feed simply triggers the operation; no race conditions or special timing are needed. AT:N: No manipulation of the attack target is required. PR:L: The attacker must be an authenticated user with sync or feed privileges to initiate a pull or feed. UI:N: No victim interaction is required; the operation runs server-side. VC:N: No confidentiality impact is evident from the patch. VI:L: The integrity impact is limited to sharing group metadata (local flag, modified timestamp, org associations) being altered by an unauthorized remote entity. VA:N: No availability impact. SC:N/SI:N/SA:N: No evidence of impact on other systems; the modification is confined to the local MISP instance's sharing group record. SI is set to N rather than L because the patch does not demonstrate that the metadata change propagates to or alters the behavior of connected MISP instances; this is an assumption recorded below.
Weakness rationale
- CWE-862 The application failed to verify that the remote server's organization was a member of the target sharing group before permitting metadata updates during pull and feed operations. The authorization check was simply absent for the non-internal remote case; only a boolean internal flag was stored and checked, with no membership validation.
Attack pattern rationale
- CAPEC-114 The remote sync user or feed process is granted the ability to modify sharing group metadata beyond what its organizational membership should permit. The authorization logic incorrectly treats any non-internal remote capture as having the same update rights as an internal one, or fails to distinguish between a remote entity that is a group member and one that is not. This is the closest CAPEC pattern to an authorization-logic flaw where the privilege boundary is miscalculated. Uncertainty: no CAPEC pattern precisely describes 'missing membership check on a shared resource update'; CAPEC-114 is selected as the best available match for an incorrectly scoped privilege.
Assumptions to verify
- The affected MISP version range is not specified in the patch; all versions prior to this commit are assumed affected.
- The PR:L assumption assumes the attacker must be an authenticated user with sync or feed privileges; the patch does not explicitly state the minimum role required.
- SI:N assumes that modifying a local sharing group's metadata does not propagate integrity changes to remote MISP instances; the patch does not provide evidence of cross-instance impact.
- The CAPEC-114 mapping is the closest available pattern; no CAPEC precisely describes a missing membership-authorization check on a shared resource update.
- The patch commit date is 2026-11-12; the actual release timeline and fixed version are unknown.
- The Co-Authored-By line credits 'Claude Opus 5.5' as a remediation developer; this is recorded as-is from the commit metadata without independent verification.
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-12 11:53 UTC Fix developed Corrective change authored (389ce674c1f8596f247bccb76a35669da691bc3c): fix: [security] Pulls and feeds no longer update sharing https://github.com/MISP/MISP/commit/389ce674c.patch
- 2026-11-19 14:12 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/MISP/MISP/commit/389ce674c.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133183",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:44:37.881472Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:44:47.659Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"app/Model/Feed.php",
"app/Model/Server.php",
"app/Model/SharingGroup.php"
],
"product": "misp",
"programFiles": [
"app/Model/Feed.php",
"app/Model/Server.php",
"app/Model/SharingGroup.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:*:*:*:*:*:*:*:*",
"versionEndIncluding": "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 flaw in the handling of remote pull and feed operations. When a non-internal pull or a feed processes incoming data and encounters an existing sharing group, the application did not verify that the remote server\u0027s organization was actually a member of that sharing group before allowing the group\u0027s metadata to be updated. The captureRemote mechanism previously stored only a boolean flag indicating whether the link was internal, and the authorization check in captureSGExisting relied solely on that flag. For non-internal pulls and feeds, the check was insufficient: a remote server whose organization was not a member of the target sharing group could still cause the group record to be modified (for example, altering the local flag, the modified timestamp, or other group properties). A feed, which has no associated server organization at all, could likewise trigger an update to an existing sharing group\u0027s metadata. The security impact is an integrity violation: an authenticated remote entity with sync or feed privileges can alter sharing group attributes that govern how data is distributed among organizations, potentially changing the local flag or other access-relevant properties of groups it does not belong to. The vulnerability requires an authenticated user with the ability to initiate a pull or feed (a sync user or feed administrator) and a target sharing group that exists on the local instance. No unauthenticated access or user interaction is required."
}
],
"impacts": [
{
"capecId": "CAPEC-114",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-114 Exploiting Incorrectly Adjusted Privileges"
}
]
}
],
"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:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"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:13:05Z",
"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"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:19:33.623Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/MISP/MISP/commit/389ce674c"
}
],
"solutions": [
{
"lang": "en",
"value": "The fix introduces a proper authorization check for remote capture operations. The captureRemote method now receives the full server context (or null for feeds) and stores both the internal flag and the remote organization identifier. A new __remoteMayUpdate method verifies that, for non-internal pulls, the remote organization is a member of the target sharing group (as owning org, in the SharingGroupOrg list, or via an all_orgs entry). For feeds (server is null), the update is always refused. When the check fails, the sharing group record is left unchanged while the pulled data still attaches to it, preserving data integrity without granting unauthorized metadata modification."
}
],
"title": "MISP: Remote Pull and Feed Operations Can Modify Sharing Group Metadata Without Organization Membership",
"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.",
"The PR:L assumption assumes the attacker must be an authenticated user with sync or feed privileges; the patch does not explicitly state the minimum role required.",
"SI:N assumes that modifying a local sharing group\u0027s metadata does not propagate integrity changes to remote MISP instances; the patch does not provide evidence of cross-instance impact.",
"The CAPEC-114 mapping is the closest available pattern; no CAPEC precisely describes a missing membership-authorization check on a shared resource update.",
"The patch commit date is 2026-11-12; the actual release timeline and fixed version are unknown.",
"The Co-Authored-By line credits \u0027Claude Opus 5.5\u0027 as a remediation developer; this is recorded as-is from the commit metadata without independent verification."
],
"capecRationale": [
{
"capecId": "CAPEC-114",
"rationale": "The remote sync user or feed process is granted the ability to modify sharing group metadata beyond what its organizational membership should permit. The authorization logic incorrectly treats any non-internal remote capture as having the same update rights as an internal one, or fails to distinguish between a remote entity that is a group member and one that is not. This is the closest CAPEC pattern to an authorization-logic flaw where the privilege boundary is miscalculated. Uncertainty: no CAPEC pattern precisely describes \u0027missing membership check on a shared resource update\u0027; CAPEC-114 is selected as the best available match for an incorrectly scoped privilege."
}
],
"commit": "389ce674c1f8596f247bccb76a35669da691bc3c",
"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: MISP is a network-accessible web application; pulls and feeds are initiated over HTTP. AC:L: An attacker with a configured pull or feed simply triggers the operation; no race conditions or special timing are needed. AT:N: No manipulation of the attack target is required. PR:L: The attacker must be an authenticated user with sync or feed privileges to initiate a pull or feed. UI:N: No victim interaction is required; the operation runs server-side. VC:N: No confidentiality impact is evident from the patch. VI:L: The integrity impact is limited to sharing group metadata (local flag, modified timestamp, org associations) being altered by an unauthorized remote entity. VA:N: No availability impact. SC:N/SI:N/SA:N: No evidence of impact on other systems; the modification is confined to the local MISP instance\u0027s sharing group record. SI is set to N rather than L because the patch does not demonstrate that the metadata change propagates to or alters the behavior of connected MISP instances; this is an assumption recorded below.",
"draft": false,
"fixSummary": "The fix introduces a proper authorization check for remote capture operations. The captureRemote method now receives the full server context (or null for feeds) and stores both the internal flag and the remote organization identifier. A new __remoteMayUpdate method verifies that, for non-internal pulls, the remote organization is a member of the target sharing group (as owning org, in the SharingGroupOrg list, or via an all_orgs entry). For feeds (server is null), the update is always refused. When the check fails, the sharing group record is left unchanged while the pulled data still attaches to it, preserving data integrity without granting unauthorized metadata modification.",
"generatedAt": "2026-11-19T14:13:05.024627Z",
"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": "74f3a4178ae1a24dd5531603002bccc8c0a264433e471b42803927e4d77b77e4",
"patchSummary": "Three files are modified. In Feed.php, two calls to SharingGroup::captureRemote change the first argument from false to null, indicating a feed has no server context. In Server.php, the pull method now passes the full $server array instead of a derived boolean. In SharingGroup.php, the static $remoteCapture variable changes from a boolean to an associative array holding internal (bool) and remote_org_id (int|null). The captureRemote method signature changes from accepting a bool to accepting an array or null. A new private method __remoteMayUpdate is added, which returns true for internal links, and for non-internal links checks that remote_org_id is set, the group is not local, and the remote org matches the group\u0027s org_id, appears in SharingGroupOrg, or is covered by an all_orgs SharingGroupServer entry. In captureSGExisting, a guard clause is inserted before the existing update logic: if a remote capture is active and __remoteMayUpdate returns false, the method returns the existing group id without further",
"patchTruncated": false,
"patches": [
{
"commit": "389ce674c1f8596f247bccb76a35669da691bc3c",
"date": "Thu, 12 Nov 2026 12:53:40 +0100",
"patchSha256": "74f3a4178ae1a24dd5531603002bccc8c0a264433e471b42803927e4d77b77e4",
"retrievedAt": "2026-11-19T14:12:22.958245Z",
"source": "https://github.com/MISP/MISP/commit/389ce674c.patch",
"sourceUrl": "https://github.com/MISP/MISP/commit/389ce674c.patch",
"subject": "fix: [security] Pulls and feeds no longer update sharing"
}
],
"source": "https://github.com/MISP/MISP/commit/389ce674c.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-19T14:13:05Z",
"version": "2.0.3"
},
"subject": "fix: [security] Pulls and feeds no longer update sharing",
"weaknessRationale": [
{
"cweId": "CWE-862",
"rationale": "The application failed to verify that the remote server\u0027s organization was a member of the target sharing group before permitting metadata updates during pull and feed operations. The authorization check was simply absent for the non-internal remote case; only a boolean internal flag was stored and checked, with no membership validation."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (389ce674c1f8596f247bccb76a35669da691bc3c): fix: [security] Pulls and feeds no longer update sharing",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/MISP/MISP/commit/389ce674c.patch"
],
"timestamp": "2026-11-12T11:53:40Z",
"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/389ce674c.patch"
],
"timestamp": "2026-11-19T14:12:22.958245Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20268"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133183",
"datePublished": "2026-11-19T14:19:33.623Z",
"dateReserved": "2026-11-19T14:19:30.159Z",
"dateUpdated": "2026-11-19T14:44:47.659Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:*"
],
"modules": [
"app/Model/Feed.php",
"app/Model/Server.php",
"app/Model/SharingGroup.php"
],
"product": "misp",
"programFiles": [
"app/Model/Feed.php",
"app/Model/Server.php",
"app/Model/SharingGroup.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 flaw in the handling of remote pull and feed operations. When a non-internal pull or a feed processes incoming data and encounters an existing sharing group, the application did not verify that the remote server\u0027s organization was actually a member of that sharing group before allowing the group\u0027s metadata to be updated. The captureRemote mechanism previously stored only a boolean flag indicating whether the link was internal, and the authorization check in captureSGExisting relied solely on that flag. For non-internal pulls and feeds, the check was insufficient: a remote server whose organization was not a member of the target sharing group could still cause the group record to be modified (for example, altering the local flag, the modified timestamp, or other group properties). A feed, which has no associated server organization at all, could likewise trigger an update to an existing sharing group\u0027s metadata. The security impact is an integrity violation: an authenticated remote entity with sync or feed privileges can alter sharing group attributes that govern how data is distributed among organizations, potentially changing the local flag or other access-relevant properties of groups it does not belong to. The vulnerability requires an authenticated user with the ability to initiate a pull or feed (a sync user or feed administrator) and a target sharing group that exists on the local instance. No unauthenticated access or user interaction is required."
}
],
"id": "CVE-2026-133183",
"lastModified": "2026-11-19T15:17:39.123",
"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:N/VI:L/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": "NONE",
"vulnIntegrityImpact": "LOW",
"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:13:05Z",
"version": "2.0.3"
}
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133183",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T14:44:37.881472Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-19T15:17:39.010",
"references": [
{
"source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"url": "https://github.com/MISP/MISP/commit/389ce674c"
}
],
"sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"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.