Threat reportVulnerabilityTL-2026-6458
Drupal Core Critical RCE via Installer Abuse (CVE-2026-132165) and Gadget Chain (CVE-2026-132166)
Drupal patched a critical flaw (CVE-2026-132165, SA-CORE-2026-017) that lets an anonymous attacker abuse install.php to attempt a reinstall of Drupal, leading to site takeover or remote code execution, plus a moderately critical gadget chain (CVE-2026-132166, SA-CORE-2026-018) that could yield RCE if untrusted data is deserialized through a separate flaw.
Key facts
| Identifiers | TL-2026-6458, CVE-2026-132165, CVE-2026-132166 |
|---|---|
| Also known as | SA-CORE-2026-017, SA-CORE-2026-018, PSA-2026-11-16, ANT-2026-GMRPK0BU |
| Severity | CRITICAL |
| First disclosed | |
| Affected products | Drupal Drupal core |
| Malware | PHP |
| MITRE ATT&CK techniques | T1059 Command and Scripting Interpreter, T1078 Valid Accounts, T1190 Exploit Public-Facing Application, T1203 Exploitation for Client Execution, T1565.001 Stored Data Manipulation, T1588.005 Exploits, T1588.006 Vulnerabilities, T1595.002 Vulnerability Scanning |
| Motivation | UNKNOWN |
| Target sectors | government administration, education, news - media, commerce, nonprofit |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 9 cited sources |
Detection coverage
As of 2026-11-19, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6458 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Web Server Process Modifying or Changing Permissions of Drupal settings.php (CVE-2026-132165) — Post-Exploitation
Detects a web server or PHP process (apache2, httpd, nginx, php, php-fpm) writing a Drupal settings.php or spawning chmod/chattr/sed/tee against it. Some CVE-2026-132165 reinstall paths only work when the web server can write to or change permissions on settings.php, and a reinstall rewrites it with attacker-chosen database settings (stored data manipulation).
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1565.001, T1222.002, T1190
- Data sources: sysmon_for_linux (index=linux, sysmon:linux), auditd, microsoft_defender_for_endpoint (DeviceFileEvents, DeviceProcessEvents)
- Severity: high
- Confidence: high
Splunk SPL
index=linux sourcetype="sysmon:linux" earliest=-24h ((EventCode=11 TargetFilename="*/sites/*/settings.php" (Image="*/php-fpm*" OR Image="*/apache2" OR Image="*/httpd" OR Image="*/nginx" OR Image="*/php*")) OR (EventCode=1 CommandLine="*settings.php*" (ParentImage="*/php-fpm*" OR ParentImage="*/apache2" OR ParentImage="*/httpd" OR ParentImage="*/nginx") (Image="*/chmod" OR Image="*/chattr" OR Image="*/sed" OR Image="*/tee" OR Image="*/cp" OR Image="*/mv")))
```comment: file-create by web worker, or helper binary spawned by web worker against settings.php```
| eval action=if(EventCode=11,"settings.php written by web process","settings.php chmod/edit spawned by web process")
| stats count AS events min(_time) AS first_seen max(_time) AS last_seen values(action) AS actions values(Image) AS images values(TargetFilename) AS files values(CommandLine) AS commands BY host user
| convert ctime(first_seen) ctime(last_seen)
| sort - eventsMicrosoft KQL
union
(DeviceFileEvents
| where Timestamp > ago(24h)
| where FileName =~ "settings.php" and ActionType in ("FileCreated", "FileModified", "FileRenamed")
| where InitiatingProcessFileName matches regex @"(?i)^(apache2|httpd|nginx|php-fpm[0-9.]*|php[0-9.]*)$"
| project Timestamp, DeviceName, AccountName = InitiatingProcessAccountName, Action = strcat("File ", ActionType), Actor = InitiatingProcessFileName, Detail = FolderPath),
(DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has "settings.php"
| where FileName in~ ("chmod", "chattr", "sed", "tee", "cp", "mv")
| where InitiatingProcessFileName matches regex @"(?i)^(apache2|httpd|nginx|php-fpm[0-9.]*)$"
| project Timestamp, DeviceName, AccountName, Action = "settings.php chmod/edit by web process", Actor = InitiatingProcessFileName, Detail = ProcessCommandLine)
| order by Timestamp descSigma
title: Drupal settings.php Modified by Web Server Process
id: 3b0d6b1e-5a52-4c8e-9a41-6458a0000003
status: experimental
description: Detects a web server or PHP-FPM process creating or modifying a Drupal sites/*/settings.php file, a precondition for some CVE-2026-132165 installer reinstall exploit paths and an indicator of database configuration tampering after takeover.
references:
- https://www.drupal.org/sa-core-2026-017
- https://www.drupal.org/sa-core-2026-018
- https://www.drupal.org/psa-2026-11-16
- https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp
author: Threadlinqs Team
date: 2026-11-19
tags:
- attack.impact
- attack.t1565.001
- attack.defense-evasion
- attack.t1222.002
- attack.initial-access
- attack.t1190
- cve.2026.132165
logsource:
category: file_event
product: linux
detection:
selection:
TargetFilename|endswith: '/settings.php'
TargetFilename|contains: '/sites/'
Image|contains:
- '/php-fpm'
- '/apache2'
- '/httpd'
- '/nginx'
condition: selection
falsepositives:
- Drupal configuration deployed by a web-process-owned deployment tool
- Initial site installation executed by the web user
level: high
Known false positives:
- Legitimate first-time Drupal installation executed under the web server account
- Deployment tooling (Drush, Composer scaffold) that runs as the web user and rewrites settings.php
- Config management agents that spawn chmod on settings.php with a web server parent
Tuning notes: Drupal hardening guidance is that settings.php is read-only and not writable by the web server, so this should be near-silent in production. Exclude CI/CD hosts and deployment windows. The php image wildcard also matches php CLI, so scope by user (www-data, apache, nginx) if drush/cron noise appears. Add an auditd watch on the settings.php path as a second telemetry source.
- Drupal Installer Path-Info Variant and Reinstall Flow Requests (CVE-2026-132165) — Exploitation · unlock with TL Creds
- Web Server or PHP-FPM Spawning Shell or Download Utility on Drupal Host (CVE-2026-132165) — Post-Exploitation · unlock with TL Creds
- Web Server or PHP-FPM Process Making Non-Standard Outbound Connections (C2 / Staging) — C2 · unlock with TL Creds
- Drupal Installer Path Probing from a Single Source (Reconnaissance for CVE-2026-132165) — Exploitation · unlock with TL Creds
- Serialized PHP Object Injection Payload in Request to Drupal (CVE-2026-132166 Gadget Chain Delivery) — Exploitation · unlock with TL Creds
- PHP File Created in Drupal Public Files Directory by Web Process (Webshell Staging) — Post-Exploitation · unlock with TL Creds
- Drupal Installer Reachable — [indicator] Request Not Blocked (CVE-2026-132165) — Exploitation · unlock with TL Creds
- Drupal Installer Access Followed by Admin Login or Admin Area Access (CVE-2026-132165) — Post-Exploitation · unlock with TL Creds
Indicators of compromise
As of 2026-11-19, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-6458.
Technical analysis
The Drupal Security Team warned that exploits might be developed within hours or days.
On 2026-11-18 the Drupal Security Team released Drupal core 10.6.22, 11.3.22 and 11.4.13, following an advance-warning PSA (PSA-2026-11-16, published 2026-11-16) that announced a release window of 17:00-21:00 UTC on 2026-11-18 and rated the pending issues Critical, with at least one exploitable by anonymous users and more than one configuration affected. The PSA also named Drupal 12.0.0-beta3 and 11.5.0-beta1 as affected, with new beta/RC builds to follow.
SA-CORE-2026-017 (CVE-2026-132165) is rated Critical (18/25; AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon). Drupal core ships core/install.php; under specific conditions an attacker can use the installer to attempt to reinstall Drupal, which can lead to site takeover or remote code execution. The advisory states that some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. The advisory lists exploit maturity as 'Proof' and notes that only uncommon configurations are exploitable. The flaw was credited to Anthropic's OSS Scanner (ANT-2026-GMRPK0BU) and reported by Lee Rowlands, Pamela Barone, Scott Euser, Stephan Zeidler and Tyler Nighswander. The advisory does not publish exploit mechanics.
SA-CORE-2026-018 (CVE-2026-132166) is rated Moderately critical (14/25; AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:Uncommon). Drupal core contains a chain of methods (a gadget chain) that could enable remote code execution if a site deserializes untrusted data through a separate vulnerability. The advisory states the issue is not directly exploitable and presents no direct threat; an attacker would first need another flaw that passes unsafe input to unserialize(). It was reported by Drupal Security Team member Drew Webber (mcdruid).
Affected versions for both: Drupal 10 before 10.6.22, 11.0.0 through 11.3.x before 11.3.22, and 11.4.0 before 11.4.13. Drupal 11.2.x and earlier, 10.5.x and earlier, and Drupal 8 and 9 are end-of-life and receive no security coverage. Mitigations: upgrade; if not possible, block /core/install.php at the web server (Apache Location block with Require all denied in the vhost, nginx 'location ^~ /core/install.php' returning 404 - not an exact-match location, because /core/install.php/foo would otherwise still reach the installer - or an .htaccess Files rule), verify that /core/install.php, /install.php and /core/install.php/foo return 403/404; Drupal Steward WAF customers are protected from known vectors.
As of the source reporting (2026-11-19) no in-the-wild exploitation, public PoC, IOCs, CVSS score or attribution had been published, NVD returned no record for CVE-2026-132165, and the CVE was not listed in CISA KEV. Context: Drupal has 5 CISA KEV entries since November 2021, two reportedly used in ransomware attacks; Drupal core SQL injection CVE-2026-9082 was exploited in May 2026 and Commerce Core access bypass CVE-2026-118539 was reported as abused. No network IOCs exist, so no BeaconBeagle correlation was applicable.
MITRE ATT&CK techniques by tactic:
Execution
T1059 Command and Scripting Interpreter; T1203 Exploitation for Client Execution
Privilege Escalation
Initial Access
T1190 Exploit Public-Facing Application
Impact
T1565.001 Stored Data Manipulation
Resource Development
T1588.005 Exploits; T1588.006 Vulnerabilities
Reconnaissance
Remediation
Patches
- Drupal 10.6.22
- Drupal 11.3.22
- Drupal 11.4.13
Immediate actions
- Upgrade Drupal core to 10.6.22, 11.3.22 or 11.4.13
- Block /core/install.php (and /install.php, /core/install.php/foo) at the web server or WAF until patched
- Ensure the web server user cannot write to or chmod settings.php
- Verify the block with curl -I against /core/install.php, /install.php and /core/install.php/foo; each must return 403 or 404
Workarounds
- Apache: <Location "/core/install.php"> Require all denied (in virtual host config, including HTTPS vhost)
- nginx: location ^~ /core/install.php { return 404; } (do not use exact match)
- Apache .htaccess: <Files "install.php"> Require all denied
- Delete core/install.php via Composer post-install-cmd/post-update-cmd scripts
- Drupal Steward WAF covers known attack vectors
Longer-term hardening
- Permanently secure the installer after installation per Drupal docs
- Migrate off end-of-life Drupal 8/9, 10.5.x and below, and 11.2.x and below
- Avoid unserialize() on untrusted input in custom and contributed code
- Reserve time for core security releases announced via PSA; update to the latest patch release ahead of the window
Affected and fixed versions
- Drupal — Drupal core
Vulnerable versions: 10.x before 10.6.22; 11.0.0 to before 11.3.22; 11.4.0 to before 11.4.13; 12.0.0-beta3 and 11.5.0-beta1 (per PSA); EOL: 8, 9, 10.5.x and below, 11.2.x and below
Fixed in: 10.6.22; 11.3.22; 11.4.13
Timeline
- CISA adds Drupal SQL injection CVE-2026-9082 to KEV after confirmed active exploitation, the most recent prior Drupal core KEV entry.
- Anthropic launches OSS Scanner, the service later credited with discovering CVE-2026-132165 (ANT-2026-GMRPK0BU).
- PSA advises updating to the latest patch release before the window, names 11.4.x, 11.3.x, 10.6.x (plus 12.0.0-beta3 and 11.5.0-beta1) as affected, and states Drupal Steward customers are protected from known vectors.
- Drupal Security Team publishes PSA-2026-11-16 announcing a Critical core release for 2026-11-18 (17:00-21:00 UTC window) and warning exploits might be developed within hours or days.
- Advisories state Drupal 8, 9, 10.5.x and below, and 11.2.x and below are end-of-life with no security coverage, leaving those sites without a patch.
- Drupal releases 10.6.22, 11.3.22 and 11.4.13 with SA-CORE-2026-017 (CVE-2026-132165, Critical, 18/25) and SA-CORE-2026-018 (CVE-2026-132166, Moderately critical, 14/25).
- NVD API query for CVE-2026-132165 returns totalResults 0, so no CVSS score, CWE or NVD description was available at research time.
- BleepingComputer reports the fixes; no in-the-wild exploitation, PoC or IOCs are public and CVE-2026-132165 is not listed in CISA KEV.
Sources cited
- Drupal Security Advisory SA-CORE-2026-017 (CVE-2026-132165) drupal.org · Advisory · 2026-11-18
- Drupal Security Advisory SA-CORE-2026-018 (CVE-2026-132166) drupal.org · Advisory · 2026-11-18
- PSA-2026-11-16: Upcoming critical core releases drupal.org · Advisory · 2026-11-16
- Drupal Security Advisories list drupal.org · Advisory · 2026-11-18
- CISA Known Exploited Vulnerabilities Catalog - Drupal CISA · Government advisory
- NVD CVE API query for CVE-2026-132165 (no record at time of research) NVD (NIST) · Advisory · 2026-11-19
- Securing the installer (install.php) - Drupal docs drupal.org · Vendor report
- Anthropic OSS Scanner red.anthropic.com · Research · 2026-10-08
- BleepingComputer: Drupal patches critical RCE flaw, warns exploits may surface quickly BleepingComputer · News · 2026-11-19
Further reading
Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.