IPCRIME NEWSROOM | NOVEMBER 19, 2026
Drupal has released critical security updates for its core content-management system after disclosing CVE-2026-132165, a vulnerability that can, under certain conditions, allow an unauthenticated attacker to misuse the installation mechanism and take over a site. The advisory was published November 18; on November 19 administrators are evaluating the new patches.
What the Drupal advisory confirms
Drupal ships an installer script to build a new site. The security team says that on certain existing installations an attacker can interact with the installer to attempt reinstalling Drupal, potentially leading to site takeover or remote code execution. The security risk is rated critical, 18 out of 25 under Drupal’s rating system. The flaw was discovered by Anthropic’s OSS Scanner; this is a confirmed vulnerability, not proof that an intrusion has occurred on any named Drupal website.
Affected and fixed versions
The security team’s supported patch recommendations are Drupal 10.6.22, Drupal 11.3.22 and Drupal 11.4.13 for sites on those respective branches. Versions 10.5 and older and Drupal 11.2 and older are outside supported security coverage. Drupal also addressed a separate, moderately critical gadget-chain issue, CVE-2026-132166, in the same security release.
A workaround is not a replacement for updating
The vendor says some exploit paths are mitigated when a web server cannot write to or change permissions on settings.php. Administrators unable to patch immediately are advised to secure the installer and its access path. Drupal Steward protects against known attack vectors but does not guarantee protection against every possible variant, so the vendor continues recommending upgrades.
IPCRIME’s defensive checklist
Identify every Drupal installation, including forgotten staging environments. Verify its branch and relevant fixed release, secure administrative and installer paths, test the change with backups in place, and check for unauthorized configuration edits or unexpected accounts if the instance was exposed. An upgrade closes the addressed flaw; it does not establish that no unauthorized access occurred beforehand.
Source documentation
- Drupal’s original SA-CORE-2026-017 advisory
- Drupal 10.6.22 release notes
- Independent November 19 coverage
Reporting based on the documents linked above. The featured image is conceptual IPCRIME artwork, not a photograph of the described incident.
