Skip to content
Fencer Intel
no cvss —

CVE-2026-132165 json

Drupal core ships with an `install.php` file for installing Drupal core.

published 7h ago modified 7h ago also DRUPAL-CORE-2026-017

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

Drupal core ships with an `install.php` file for installing Drupal core.

Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal. This can lead to a site takeover or remote code execution.

Some exploit paths are mitigated if the web server cannot write to or change permissions on `settings.php`. In addition to upgrading, the Drupal Security Team recommends [securing the Drupal installer](https://www.drupal.org/docs/administering-a-drupal-site/security-in-drupal/securing-the-installer-installphp) after installation.

*Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU.*

#### Drupal Steward protection:

This issue is being protected by [Drupal Steward](https://www.drupal.org/steward). Sites that use Drupal Steward are already protected from some known attack vectors, but the protection offered will not cover all possible exploits. Sites should upgrade in the near future in case additional attack vectors are discovered.

Patch / fix

  • packagist drupal/core 10.6.22, 11.3.22, 11.4.13

Is CVE-2026-132165 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist drupal/core
<10.6.22
>=11.0.0, <11.3.22
>=11.4.0, <11.4.13
10.6.22
11.3.22
11.4.13

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.