Skip to content
Critical Remote Code Execution Flaw in Drupal Installer Disclosed

Critical Remote Code Execution Flaw in Drupal Installer Disclosed

First seen 19 Nov 2026, 22:51 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 19, 2026 at 22:52 UTC
  • •CVE-2026-132165 allows remote code execution via the Drupal installer.
  • •All supported Drupal core versions prior to 10.6.22, 11.3.22, and 11.4.13 are affected.
  • •No exploitation in the wild has been reported, but the vulnerability is rated critical.

Drupal has announced a critical vulnerability, CVE-2026-132165, in its core installer that allows unauthenticated attackers to potentially reinstall a live site via install.php, leading to site takeover or remote code execution. This flaw affects all supported Drupal core versions prior to 10.6.22, 11.3.22, and 11.4.13. The vulnerability was disclosed in advisory SA-CORE-2026-017 on November 18, 2026, and patches are now available. The attack requires no authentication and can be executed remotely if the install.php file is accessible. While no exploitation has been reported in the wild, the risk remains significant due to the nature of the vulnerability. Drupal rates the flaw as critical at 18 out of 25 on its risk scale, citing that exploitation may require complex configurations. Users are urged to upgrade to the latest versions to mitigate risks.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-18
Vulnerability disclosed
Drupal announced CVE-2026-132165, a critical flaw in the installer allowing site takeover.
Drupal
2026-11-19
Patches released
Drupal released updates for all affected versions to address the critical vulnerability.
Cyberkendra

More articles in this cluster (3)

Following this threat?

Track CVE-2026-132165 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions of Drupal are affected?
All supported Drupal core versions before 10.6.22, 11.3.22, and 11.4.13 are vulnerable.
What should I do if I'm using an affected version?
Upgrade to the latest versions: 10.6.22, 11.3.22, or 11.4.13 to mitigate the risk.
Has this vulnerability been exploited in the wild?
No exploitation has been reported as of now, but the vulnerability is considered critical.