CVE-2026-45959 (GCVE-0-2026-45959)
Vulnerability from cvelistv5 – Published: 2026-05-27 12:18 – Updated: 2026-10-19 19:26- CWE-787 - Out-of-bounds Write
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
a71475582ada92ba021852bf3c2b40ab3718549b , < 9a3ace9b010ffd8c422c97844ae152f7c53d6b18
(git)
Affected: a71475582ada92ba021852bf3c2b40ab3718549b , < 90f9090e3e744a8fe3bb6fa0e61f577347728b0b (git) Affected: a71475582ada92ba021852bf3c2b40ab3718549b , < d5abcc33ee76bc26d58b39dc1a097e43a99dd438 (git) |
guessed | |
| Linux | Linux |
Affected:
6.17
Unaffected: 0 , < 6.17 (semver) Unaffected: 6.18.14 , ≤ 6.18.* (semver) Unaffected: 6.19.4 , ≤ 6.19.* (semver) Unaffected: 7.0 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-45959",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T15:18:37.644714Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-787",
"description": "CWE-787 Out-of-bounds Write",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T19:26:40.585Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/crypto/ccp/ccp-ops.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "9a3ace9b010ffd8c422c97844ae152f7c53d6b18",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
},
{
"lessThan": "90f9090e3e744a8fe3bb6fa0e61f577347728b0b",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
},
{
"lessThan": "d5abcc33ee76bc26d58b39dc1a097e43a99dd438",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/crypto/ccp/ccp-ops.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.14",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.4",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "6.17",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Fix a crash due to incorrect cleanup usage of kfree\n\nAnnotating a local pointer variable, which will be assigned with the\nkmalloc-family functions, with the `__cleanup(kfree)` attribute will\nmake the address of the local variable, rather than the address returned\nby kmalloc, passed to kfree directly and lead to a crash due to invalid\ndeallocation of stack address. According to other places in the repo,\nthe correct usage should be `__free(kfree)`. The code coincidentally\ncompiled because the parameter type `void *` of kfree is compatible with\nthe desired type `struct { ... } **`."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The vulnerable AES-GCM path is reached through the local AF_ALG crypto socket interface (socket/bind/sendmsg syscalls), explicitly selectable via the \"gcm-aes-ccp\" driver name; there is no remote network peer required in the reliable trigger path.\nAC:L - The incorrect cleanup fires on every return from ccp_run_aes_gcm_cmd, so a single AES-GCM operation deterministically triggers the invalid free with no race, timing, or memory-layout condition the attacker must defeat.\nPR:L - Creating an AF_ALG socket and submitting a gcm(aes) request requires only a basic unprivileged local account with no capability; no root or special privilege is needed.\nUI:N - The attacker submits the crypto request entirely on its own; no victim action or separate user interaction is required.\nS:U - The invalid free corrupts and crashes within the kernel\u0027s own security authority and crosses no VM, sandbox, or IOMMU boundary.\nC:H - This is an invalid free (memory-corruption class, not a NULL deref); per UAF/corruption guidance the allocator\u0027s mishandling of the stack pointer can disturb slab state and freed-object contents, which can be leveraged toward information disclosure.\nI:H - Feeding kfree a stack address drives the SLUB allocator to write freelist pointers / drop refcounts on memory it never owned, a corruption primitive that per UAF/double-free guidance can be leveraged into a write affecting control flow.\nA:H - The bug deterministically passes a stack address to kfree on every invocation, causing an immediate kernel oops/panic (DoS) that any unprivileged local user can trigger repeatedly."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:28:57.463Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/9a3ace9b010ffd8c422c97844ae152f7c53d6b18"
},
{
"url": "https://git.kernel.org/stable/c/90f9090e3e744a8fe3bb6fa0e61f577347728b0b"
},
{
"url": "https://git.kernel.org/stable/c/d5abcc33ee76bc26d58b39dc1a097e43a99dd438"
}
],
"title": "crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-45959",
"datePublished": "2026-05-27T12:18:16.039Z",
"dateReserved": "2026-05-13T15:03:33.089Z",
"dateUpdated": "2026-10-19T19:26:40.585Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-45959",
"date": "2026-11-19",
"epss": "0.00128",
"percentile": "0.02493"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/crypto/ccp/ccp-ops.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "9a3ace9b010ffd8c422c97844ae152f7c53d6b18",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
},
{
"lessThan": "90f9090e3e744a8fe3bb6fa0e61f577347728b0b",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
},
{
"lessThan": "d5abcc33ee76bc26d58b39dc1a097e43a99dd438",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/crypto/ccp/ccp-ops.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "26EE06AD-A558-4B3A-9C7C-9EBD5CF65449",
"versionEndExcluding": "6.18.14",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "672A3E79-EC03-479D-8503-361DFBDC8092",
"versionEndExcluding": "6.19.4",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Fix a crash due to incorrect cleanup usage of kfree\n\nAnnotating a local pointer variable, which will be assigned with the\nkmalloc-family functions, with the `__cleanup(kfree)` attribute will\nmake the address of the local variable, rather than the address returned\nby kmalloc, passed to kfree directly and lead to a crash due to invalid\ndeallocation of stack address. According to other places in the repo,\nthe correct usage should be `__free(kfree)`. The code coincidentally\ncompiled because the parameter type `void *` of kfree is compatible with\nthe desired type `struct { ... } **`."
}
],
"id": "CVE-2026-45959",
"lastModified": "2026-10-19T20:18:22.440",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-45959",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T15:18:37.644714Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-05-27T14:17:12.543",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/90f9090e3e744a8fe3bb6fa0e61f577347728b0b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/9a3ace9b010ffd8c422c97844ae152f7c53d6b18"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/d5abcc33ee76bc26d58b39dc1a097e43a99dd438"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-476"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-787"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-06T04:52:05+00:00",
"cve": "CVE-2026-45959",
"id": "CVE-2026-45959",
"initial_release_date": "2026-05-27T00:00:00+00:00",
"product_status:fixed": "612",
"product_status:known_not_affected": "112",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45959.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-10-17T00:30:18Z",
"cve": "CVE-2026-45959",
"id": "CVE-2026-45959",
"initial_release_date": "2026-05-28T03:55:25Z",
"product_status:known_affected": "0",
"product_status:known_not_affected": "385",
"product_status:recommended": "80",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-45959",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-45959.json",
"version": "6"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-45959",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-16T15:18:37.644714Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-787",
"description": "CWE-787 Out-of-bounds Write",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-16T15:18:39.052Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/crypto/ccp/ccp-ops.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "9a3ace9b010ffd8c422c97844ae152f7c53d6b18",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
},
{
"lessThan": "90f9090e3e744a8fe3bb6fa0e61f577347728b0b",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
},
{
"lessThan": "d5abcc33ee76bc26d58b39dc1a097e43a99dd438",
"status": "affected",
"version": "a71475582ada92ba021852bf3c2b40ab3718549b",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/crypto/ccp/ccp-ops.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.14",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.4",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "6.17",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Fix a crash due to incorrect cleanup usage of kfree\n\nAnnotating a local pointer variable, which will be assigned with the\nkmalloc-family functions, with the `__cleanup(kfree)` attribute will\nmake the address of the local variable, rather than the address returned\nby kmalloc, passed to kfree directly and lead to a crash due to invalid\ndeallocation of stack address. According to other places in the repo,\nthe correct usage should be `__free(kfree)`. The code coincidentally\ncompiled because the parameter type `void *` of kfree is compatible with\nthe desired type `struct { ... } **`."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The vulnerable AES-GCM path is reached through the local AF_ALG crypto socket interface (socket/bind/sendmsg syscalls), explicitly selectable via the \"gcm-aes-ccp\" driver name; there is no remote network peer required in the reliable trigger path.\nAC:L - The incorrect cleanup fires on every return from ccp_run_aes_gcm_cmd, so a single AES-GCM operation deterministically triggers the invalid free with no race, timing, or memory-layout condition the attacker must defeat.\nPR:L - Creating an AF_ALG socket and submitting a gcm(aes) request requires only a basic unprivileged local account with no capability; no root or special privilege is needed.\nUI:N - The attacker submits the crypto request entirely on its own; no victim action or separate user interaction is required.\nS:U - The invalid free corrupts and crashes within the kernel\u0027s own security authority and crosses no VM, sandbox, or IOMMU boundary.\nC:H - This is an invalid free (memory-corruption class, not a NULL deref); per UAF/corruption guidance the allocator\u0027s mishandling of the stack pointer can disturb slab state and freed-object contents, which can be leveraged toward information disclosure.\nI:H - Feeding kfree a stack address drives the SLUB allocator to write freelist pointers / drop refcounts on memory it never owned, a corruption primitive that per UAF/double-free guidance can be leveraged into a write affecting control flow.\nA:H - The bug deterministically passes a stack address to kfree on every invocation, causing an immediate kernel oops/panic (DoS) that any unprivileged local user can trigger repeatedly."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:28:57.463Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/9a3ace9b010ffd8c422c97844ae152f7c53d6b18"
},
{
"url": "https://git.kernel.org/stable/c/90f9090e3e744a8fe3bb6fa0e61f577347728b0b"
},
{
"url": "https://git.kernel.org/stable/c/d5abcc33ee76bc26d58b39dc1a097e43a99dd438"
}
],
"title": "crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-45959",
"datePublished": "2026-05-27T12:18:16.039Z",
"dateReserved": "2026-05-13T15:03:33.089Z",
"dateUpdated": "2026-10-19T19:26:40.585Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
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.