NCSC-2026-0507
Vulnerability from csaf_ncscnl - Published: 2026-11-18 19:01 - Updated: 2026-11-18 19:01Drupal core contains a potential gadget chain for insecure deserialization that could enable remote code execution if combined with another vulnerability allowing unsafe input to be unserialized.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
vers:unknown/*
Drupal / core
|
vers:unknown/* |
Drupal core's install.php can be exploited to attempt a reinstall, potentially enabling site takeover or remote code execution under certain conditions.
| URL | Category |
|---|---|
| https://www.drupal.org/sa-core-2026-017 | external |
| https://www.drupal.org/sa-core-2026-018 | external |
| https://www.drupal.org/security | external |
| https://vulnerabilities.ncsc.nl/csaf/v2/2026/cve-… | self |
| https://vulnerabilities.ncsc.nl/csaf/v2/2026/cve-… | self |
{
"document": {
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "nl",
"notes": [
{
"category": "legal_disclaimer",
"text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this page to enhance access to its information and security advisories. The use of this security advisory is subject to the following terms and conditions:\n\n NCSC-NL makes every reasonable effort to ensure that the content of this page is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or continuous keeping up-to-date. The information contained in this security advisory is intended solely for the purpose of providing general information to professional users. No rights can be derived from the information provided therein.\n\n NCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of this security advisory. This includes damage resulting from the inaccuracy of incompleteness of the information contained in the advisory.\n This security advisory is subject to Dutch law. All disputes related to or arising from the use of this advisory will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings."
},
{
"category": "description",
"text": "Drupal heeft kwetsbaarheden verholpen in Drupal core.",
"title": "Feiten"
},
{
"category": "description",
"text": "De eerste kwetsbaarheid betreft een potenti\u00eble gadget chain gerelateerd aan onveilige deserialisatie binnen Drupal core. Deze kwetsbaarheid is op zichzelf niet direct exploiteerbaar, maar kan worden misbruikt in combinatie met een andere fout die het mogelijk maakt onveilige input te deserialiseren, wat kan leiden tot remote code execution. De tweede kwetsbaarheid betreft het install.php-script van Drupal core, dat onder specifieke omstandigheden kan worden misbruikt om een site opnieuw te installeren. Dit gebeurt wanneer de installer niet correct is beveiligd of verwijderd na de initi\u00eble installatie, waardoor een aanvaller arbitrary code kan uitvoeren of de controle over de site kan overnemen door authenticatie- en configuratiecontroles te omzeilen.",
"title": "Interpretaties"
},
{
"category": "description",
"text": "Drupal heeft updates uitgebracht om deze kwetsbaarheden in Drupal core te verhelpen. Zie bijgevoegde referenties voor meer informatie.",
"title": "Oplossingen"
},
{
"category": "general",
"text": "medium",
"title": "Kans"
},
{
"category": "general",
"text": "high",
"title": "Schade"
},
{
"category": "general",
"text": "Missing Authentication for Critical Functionality",
"title": "CWE-306"
},
{
"category": "general",
"text": "Deserialization of Untrusted Data",
"title": "CWE-502"
}
],
"publisher": {
"category": "coordinator",
"contact_details": "cert@ncsc.nl",
"name": "Nationaal Cyber Security Centrum",
"namespace": "https://www.ncsc.nl/"
},
"references": [
{
"category": "external",
"summary": "Reference",
"url": "https://www.drupal.org/sa-core-2026-017"
},
{
"category": "external",
"summary": "Reference",
"url": "https://www.drupal.org/sa-core-2026-018"
},
{
"category": "external",
"summary": "Reference",
"url": "https://www.drupal.org/security"
}
],
"title": "Kwetsbaarheden verholpen in Drupal core",
"tracking": {
"current_release_date": "2026-11-18T19:01:09.046915Z",
"generator": {
"date": "2025-08-04T16:30:00Z",
"engine": {
"name": "V.A.",
"version": "1.3"
}
},
"id": "NCSC-2026-0507",
"initial_release_date": "2026-11-18T19:01:09.046915Z",
"revision_history": [
{
"date": "2026-11-18T19:01:09.046915Z",
"number": "1.0.0",
"summary": "Initiele versie"
}
],
"status": "final",
"version": "1.0.0"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "vers:unknown/*",
"product": {
"name": "vers:unknown/*",
"product_id": "CSAFPID-1"
}
}
],
"category": "product_name",
"name": "core"
}
],
"category": "vendor",
"name": "Drupal"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2026-132166",
"notes": [
{
"category": "description",
"text": "Drupal core contains a potential gadget chain for insecure deserialization that could enable remote code execution if combined with another vulnerability allowing unsafe input to be unserialized.",
"title": "Summary"
}
],
"product_status": {
"known_affected": [
"CSAFPID-1"
]
},
"references": [
{
"category": "self",
"summary": "CVE-2026-132166 | NCSC-NL Website",
"url": "https://vulnerabilities.ncsc.nl/csaf/v2/2026/cve-2026-132166.json"
}
],
"title": "CVE-2026-132166"
},
{
"cve": "CVE-2026-132165",
"notes": [
{
"category": "description",
"text": "Drupal core\u0027s install.php can be exploited to attempt a reinstall, potentially enabling site takeover or remote code execution under certain conditions.",
"title": "Summary"
}
],
"product_status": {
"known_affected": [
"CSAFPID-1"
]
},
"references": [
{
"category": "self",
"summary": "CVE-2026-132165 | NCSC-NL Website",
"url": "https://vulnerabilities.ncsc.nl/csaf/v2/2026/cve-2026-132165.json"
}
],
"title": "CVE-2026-132165"
}
]
}
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.