CVE-2026-119623 (GCVE-0-2026-119623)
Vulnerability from cvelistv5 – Published: 2026-11-17 11:11 – Updated: 2026-11-17 11:43- CWE-306 - Missing Authentication for Critical Functionality
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| TYPO3 | TYPO3 CMS |
Affected:
14.0.0 , < 14.3.12
(semver)
Affected: 13.0.0 , < 13.4.40 (semver) Affected: 12.0.0 , < 12.4.52 (semver) Affected: 11.0.0 , < 11.5.57 (semver) Affected: 10.0.0 , < 10.4.63 (semver) cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:* cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:* cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:* cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:* cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-119623",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T11:30:26.507943Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T11:43:55.377Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://packagist.org",
"defaultStatus": "unaffected",
"modules": [
"Installer"
],
"packageName": "typo3/cms-install",
"product": "TYPO3 CMS",
"repo": "https://github.com/TYPO3/typo3",
"vendor": "TYPO3",
"versions": [
{
"lessThan": "14.3.12",
"status": "affected",
"version": "14.0.0",
"versionType": "semver"
},
{
"lessThan": "13.4.40",
"status": "affected",
"version": "13.0.0",
"versionType": "semver"
},
{
"lessThan": "12.4.52",
"status": "affected",
"version": "12.0.0",
"versionType": "semver"
},
{
"lessThan": "11.5.57",
"status": "affected",
"version": "11.0.0",
"versionType": "semver"
},
{
"lessThan": "10.4.63",
"status": "affected",
"version": "10.0.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "14.3.12",
"versionStartIncluding": "14.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "13.4.40",
"versionStartIncluding": "13.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "12.4.52",
"versionStartIncluding": "12.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "11.5.57",
"versionStartIncluding": "11.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.4.63",
"versionStartIncluding": "10.0.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "0xkidz"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Torben Hansen"
}
],
"datePublic": "2026-11-17T10:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with \u003ci\u003eFIRST_INSTALL\u003c/i\u003e in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to \u003cstrong\u003eremote code execution\u003c/strong\u003e. As demonstrated in\u003ca href=\"https://news.typo3.com/security/advisory/typo3-core-sa-2026-026\"\u003e TYPO3-CORE-SA-2026-026\u003c/a\u003e, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.\u003c/p\u003e\n\u003cp\u003eWith the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting \u003ci\u003e$GLOBALS[\u0027TYPO3_CONF_VARS\u0027][\u0027SYS\u0027][\u0027isInstalling\u0027]\u003c/i\u003e is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names \u003ci\u003eFIRST_INSTALL\u003c/i\u003e and \u003ci\u003eFIRST_INSTALL.txt\u003c/i\u003e are accepted as marker files.\u003c/p\u003e"
}
],
"value": "The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.\n\nWith the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS[\u0027TYPO3_CONF_VARS\u0027][\u0027SYS\u0027][\u0027isInstalling\u0027] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files."
}
],
"metrics": [
{
"cvssV4_0": {
"baseScore": 9.4,
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
"version": "4.0"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306 Missing Authentication for Critical Functionality",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T11:42:04.563Z",
"orgId": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"shortName": "TYPO3"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://news.typo3.com/security/advisory/typo3-core-sa-2026-027"
},
{
"name": "Git commit of 13.4 branch",
"tags": [
"patch"
],
"url": "https://github.com/TYPO3/typo3/commit/0f0a1ca5a5eae9349a38e6d34b096c01d9bf6d1d"
},
{
"name": "Git commit of 14.3 branch",
"tags": [
"patch"
],
"url": "https://github.com/TYPO3/typo3/commit/3ad2358f8208dc5258880ad4880c244123c5edf2"
},
{
"name": "Git commit of main branch",
"tags": [
"patch"
],
"url": "https://github.com/TYPO3/typo3/commit/1634e72112a69435759336cb363daac6d35956bc"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "TYPO3 CMS - Missing Authentication in Installer",
"x_generator": {
"engine": "seads"
}
}
},
"cveMetadata": {
"assignerOrgId": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"assignerShortName": "TYPO3",
"cveId": "CVE-2026-119623",
"datePublished": "2026-11-17T11:11:04.860Z",
"dateReserved": "2026-10-30T12:41:09.030Z",
"dateUpdated": "2026-11-17T11:43:55.377Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://packagist.org",
"defaultStatus": "unaffected",
"modules": [
"Installer"
],
"packageName": "typo3/cms-install",
"product": "TYPO3 CMS",
"repo": "https://github.com/TYPO3/typo3",
"vendor": "TYPO3",
"versions": [
{
"lessThan": "14.3.12",
"status": "affected",
"version": "14.0.0",
"versionType": "semver"
},
{
"lessThan": "13.4.40",
"status": "affected",
"version": "13.0.0",
"versionType": "semver"
},
{
"lessThan": "12.4.52",
"status": "affected",
"version": "12.0.0",
"versionType": "semver"
},
{
"lessThan": "11.5.57",
"status": "affected",
"version": "11.0.0",
"versionType": "semver"
},
{
"lessThan": "10.4.63",
"status": "affected",
"version": "10.0.0",
"versionType": "semver"
}
]
}
],
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.\n\nWith the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS[\u0027TYPO3_CONF_VARS\u0027][\u0027SYS\u0027][\u0027isInstalling\u0027] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files."
}
],
"id": "CVE-2026-119623",
"lastModified": "2026-11-17T12:17:44.280",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 9.4,
"baseSeverity": "CRITICAL",
"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": "HIGH",
"subConfidentialityImpact": "HIGH",
"subIntegrityImpact": "HIGH",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-119623",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T11:30:26.507943Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-17T11:17:24.740",
"references": [
{
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"url": "https://github.com/TYPO3/typo3/commit/0f0a1ca5a5eae9349a38e6d34b096c01d9bf6d1d"
},
{
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"url": "https://github.com/TYPO3/typo3/commit/1634e72112a69435759336cb363daac6d35956bc"
},
{
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"url": "https://github.com/TYPO3/typo3/commit/3ad2358f8208dc5258880ad4880c244123c5edf2"
},
{
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"url": "https://news.typo3.com/security/advisory/typo3-core-sa-2026-027"
}
],
"sourceIdentifier": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-306"
}
],
"source": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-119623",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T11:30:26.507943Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T11:41:24.853Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://packagist.org",
"defaultStatus": "unaffected",
"modules": [
"Installer"
],
"packageName": "typo3/cms-install",
"product": "TYPO3 CMS",
"repo": "https://github.com/TYPO3/typo3",
"vendor": "TYPO3",
"versions": [
{
"lessThan": "14.3.12",
"status": "affected",
"version": "14.0.0",
"versionType": "semver"
},
{
"lessThan": "13.4.40",
"status": "affected",
"version": "13.0.0",
"versionType": "semver"
},
{
"lessThan": "12.4.52",
"status": "affected",
"version": "12.0.0",
"versionType": "semver"
},
{
"lessThan": "11.5.57",
"status": "affected",
"version": "11.0.0",
"versionType": "semver"
},
{
"lessThan": "10.4.63",
"status": "affected",
"version": "10.0.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "14.3.12",
"versionStartIncluding": "14.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "13.4.40",
"versionStartIncluding": "13.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "12.4.52",
"versionStartIncluding": "12.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "11.5.57",
"versionStartIncluding": "11.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:*",
"versionEndExcluding": "10.4.63",
"versionStartIncluding": "10.0.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "0xkidz"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Torben Hansen"
}
],
"datePublic": "2026-11-17T10:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eThe installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with \u003ci\u003eFIRST_INSTALL\u003c/i\u003e in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to \u003cstrong\u003eremote code execution\u003c/strong\u003e. As demonstrated in\u003ca href=\"https://news.typo3.com/security/advisory/typo3-core-sa-2026-026\"\u003e TYPO3-CORE-SA-2026-026\u003c/a\u003e, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.\u003c/p\u003e\n\u003cp\u003eWith the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting \u003ci\u003e$GLOBALS[\u0027TYPO3_CONF_VARS\u0027][\u0027SYS\u0027][\u0027isInstalling\u0027]\u003c/i\u003e is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names \u003ci\u003eFIRST_INSTALL\u003c/i\u003e and \u003ci\u003eFIRST_INSTALL.txt\u003c/i\u003e are accepted as marker files.\u003c/p\u003e"
}
],
"value": "The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way.\n\nWith the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS[\u0027TYPO3_CONF_VARS\u0027][\u0027SYS\u0027][\u0027isInstalling\u0027] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files."
}
],
"metrics": [
{
"cvssV4_0": {
"baseScore": 9.4,
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
"version": "4.0"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306 Missing Authentication for Critical Functionality",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T11:42:04.563Z",
"orgId": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"shortName": "TYPO3"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://news.typo3.com/security/advisory/typo3-core-sa-2026-027"
},
{
"name": "Git commit of 13.4 branch",
"tags": [
"patch"
],
"url": "https://github.com/TYPO3/typo3/commit/0f0a1ca5a5eae9349a38e6d34b096c01d9bf6d1d"
},
{
"name": "Git commit of 14.3 branch",
"tags": [
"patch"
],
"url": "https://github.com/TYPO3/typo3/commit/3ad2358f8208dc5258880ad4880c244123c5edf2"
},
{
"name": "Git commit of main branch",
"tags": [
"patch"
],
"url": "https://github.com/TYPO3/typo3/commit/1634e72112a69435759336cb363daac6d35956bc"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "TYPO3 CMS - Missing Authentication in Installer",
"x_generator": {
"engine": "seads"
}
}
},
"cveMetadata": {
"assignerOrgId": "f4fb688c-4412-4426-b4b8-421ecf27b14a",
"assignerShortName": "TYPO3",
"cveId": "CVE-2026-119623",
"datePublished": "2026-11-17T11:11:04.860Z",
"dateReserved": "2026-10-30T12:41:09.030Z",
"dateUpdated": "2026-11-17T11:43:55.377Z",
"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.