Today's cybersecurity headlines are brought to you by ThreatPerspective


Ethical Hacking News

Critical Vulnerability in Drupal Core Exposes Sites to Remote Code Execution and Site Takeover




A critical vulnerability in Drupal core has been discovered, exposing sites to remote code execution and site takeover. The vulnerability, tracked as CVE-2026-132165, was disclosed by the Drupal Security Team and rated as critical, with a risk scale of 18 out of 25. Site owners are advised to update to the latest releases and implement additional security measures to prevent exploitation of this vulnerability.



  • Drupal has been hit with a critical vulnerability (CVE-2026-132165) that could grant unauthenticated attackers control of sites.
  • The vulnerability arises from a critical flaw in the core's installer, allowing attackers to reinstall a site and potentially take over it.
  • Site owners must block the installer and take proactive steps to prevent exploitation, as the vulnerability is rated critical (18/25).
  • The vulnerability affects every release below 10.6.22, as well as Drupal 11 releases from 11.0.0 before 11.3.22 and from 11.4.0 before 11.4.13.
  • Fixed versions of the vulnerable releases have been made available, and site owners should apply these updates as soon as possible.
  • Additional security measures, such as blocking the installer or using the Drupal Steward protection service, are recommended to prevent exploitation.



  • The Drupal community has been left reeling in the aftermath of a newly discovered critical vulnerability that could potentially grant unauthenticated attackers control of sites. The vulnerability, tracked as CVE-2026-132165, was disclosed by the Drupal Security Team and rated as critical, with a risk scale of 18 out of 25.

    According to the Drupal Security Team, the vulnerability arises from a critical flaw in the core's installer, which allows an attacker without login credentials to use the built-in installer to attempt to reinstall a site. This can lead to a site takeover or remote code execution, with the project rating the vulnerable configurations as uncommon.

    The installer, which ships in every copy of Drupal core as the file /core/install.php, stays on the site after installation. However, core's default .htaccess rules do not block requests to it, leaving the protection of this file up to each site. This means that site owners will need to take proactive steps to block the installer and prevent exploitation of this vulnerability.

    The Drupal Security Team had warned site owners in an advance notice earlier this week to set aside time for the update, warning that exploits may be developed within hours or days. Every release below 10.6.22 is affected, along with Drupal 11 releases from 11.0.0 before 11.3.22 and from 11.4.0 before 11.4.13.

    Fortunately, fixed versions of the vulnerable releases have been made available, with detailed release notes provided by the Drupal Security Team. These include updates to Drupal 11.4.x, 11.3.x, and 10.6.x, which should be applied as soon as possible to prevent exploitation of this vulnerability.

    In addition to updating to the latest releases, site owners are advised to block the installer even after updating. Sites that cannot update yet should follow the project's installer guidance, which describes three options: a deny rule in the web server configuration, an .htaccess rule, or removing the file and keeping it removed with Composer scripts.

    Sites that use the Drupal Steward protection service are already protected from known attack vectors, according to the team, and should still update in case new vectors emerge. However, the Drupal Security Team has noted that the 11.3.x branch and Drupal 10 lose security coverage altogether in December under the project's support schedule.

    The vulnerability was discovered by Anthropic's OSS Scanner, an automated service the AI company launched on October 8 to look for vulnerabilities in open-source projects that opt in. Findings go to maintainers without human review, each with a reproducer and, where available, a candidate patch.

    This is the second critical remote code execution flaw fixed in Drupal core in two months, after the Field UI flaw patched on October 14, which also had at least one exploit path that needed no login. The increasing frequency of critical vulnerabilities in Drupal core highlights the need for site owners to stay vigilant and keep their sites up to date.

    The Drupal Security Team has also noted that a surge of security reports, which it attributes to AI tools, is more than it can sustain at its current funding, and that it is cutting security coverage for core minor versions from 12 months to 8 starting in 2027.

    In light of this vulnerability, it is essential for site owners to take immediate action to protect their sites. This includes updating to the latest releases, blocking the installer, and implementing additional security measures to prevent exploitation of this vulnerability.



    Related Information:
  • https://www.ethicalhackingnews.com/articles/Critical-Vulnerability-in-Drupal-Core-Exposes-Sites-to-Remote-Code-Execution-and-Site-Takeover-ehn.shtml

  • https://thehackernews.com/2026/11/drupal-patches-critical-installer-flaw.html


  • Published: Thu Nov 19 09:56:11 2026 by llama3.2 3B Q4_K_M













    © Ethical Hacking News . All rights reserved.

    Privacy | Terms of Use | Contact Us