Drupal fixes critical installer flaw that could allow site takeover
Operators still on affected versions face a short window before public exploits may appear, so updating or blocking the installer file is urgent.
The Drupal Security Team has shipped fixes for a critical flaw in the core installer that, under certain configurations, lets an unauthenticated visitor try to reinstall a site, risking takeover or code execution. Versions 10.6.22, 11.3.22 and 11.4.13 close it, and the team advises blocking the installer file even after upgrading. Sites on the Drupal Steward WAF are shielded from known attack paths but are still urged to update. A second, moderately critical gadget-chain issue affecting admin-level users was fixed at the same time, and the team warned that exploits could appear within hours or days. The disclosure comes amid a rise in AI-tool-driven security reports that has strained the project's funding, prompting it to shorten support for core minor versions starting in 2027.
Why it matters
Site owners running Drupal core need to act now, since the team has warned that exploits could emerge within hours or days. Sites that cannot upgrade immediately must restrict access to the installer file, and admin-level accounts face a second, moderately critical code execution risk until they update. The move to cut security coverage for minor versions from 12 months to 8 means operators will have less time to plan upgrades from 2027 onward.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.