Drupal released a critical core fix on October 14 and followed it with 34 contributed module advisories on October 21. Thirty-nine advisories in eight days, ten of them rated critical or highly critical, landed in the same week as PHP2Shell. For an association with one Drupal site and a part-time webmaster, that is a list nobody has time to read line by line.
So we read it, and checked each module against the number of sites that actually report using it. The severity rating tells you how bad a flaw is. The install count tells you whether it is likely to be yours. You need both.
Where this comes from. Every advisory and project page on drupal.org, read directly. Install counts are the figures each project page reports. None of these advisories reports exploitation in the wild as of this writing.
Start With Core, Because Everyone Runs It
SA-CORE-2026-014, rated critical, is a remote code execution flaw in the Field UI module. Drupal says it is not directly exploitable with core alone, but that contributed modules create serious exploit paths, and that at least one known path does not require logging in.
- Fixed in. Drupal 11.4.10, 11.3.19 and 10.6.19. The same releases fix two moderately critical cross-site scripting issues published the same day.
- If you cannot update today. Uninstall the Field UI module until you can update. It is the admin screen for managing fields, so most sites can live without it for a few days.
- If you are on an old minor version. Drupal 11.2 and earlier, Drupal 10.5 and earlier, and Drupal 8 and 9 get no fix. If your site is on one of those, the update is the fix, and it is now urgent.
And note the date. Drupal 10.6.19 fixes this for Drupal 10 today. After Drupal 10 reaches end of life on December 9, the next core flaw like this one will not be fixed for Drupal 10 at all.
The Modules You Are Most Likely to Have
Ranked by reported installs. All of these are rated moderately critical, and most require an attacker to already have some level of access. That is why they are lower on the severity scale and higher on your list.
- Gin Admin Theme. 147,216 sites. Cross-site scripting that requires a role able to enter certain HTML or administer menus. Fixed in 4.1.4 and 5.0.16.
- Bootstrap theme. 91,201 sites. Cross-site scripting through tooltip and popover attributes, exploitable in the default configuration by a user with an account. Fixed in 8.x-3.45. If you cannot update, turn off tooltips and popovers in the theme settings.
- Rabbit Hole. 74,799 sites. Anonymous visitors can get past Rabbit Hole's hide and redirect rules with a query parameter. If you use it to hide pages that were never meant to be reached, those pages were reachable. Fixed in 8.x-1.3.
- View Unpublished. 72,852 sites. Multilingual sites only: it can override other access modules for translations of content that is partly unpublished. Fixed in 8.x-1.5.
- Shield. 27,674 sites. No limit on password attempts, so the password protecting a site can be brute-forced. Drupal notes a long, randomly generated password is not practically guessable. Fixed in 8.x-1.9.
- Simple OAuth and OpenID Connect. 27,587 sites. Cached token permissions can carry over to another user's token with the same scopes, up to administrator access. Fixed in 6.1.3. If your member login or an AMS connection uses OAuth through Drupal, this is the one to prioritize.
- Domain. 12,188 sites. An access bypass in Domain Access that depends on a setting that is off by default. Fixed in 3.0.2.
Shield Deserves a Second Look
Shield is what a lot of agencies use to put a password in front of staging and development sites. Those sites usually run the same code and often hold a copy of the live database, including member records. A staging site behind a short, shared password that everyone on the project has known for three years is exactly the case this advisory describes. Update it, and while you are there, replace the password with a long random one.
The Alarming Ones Are Mostly Not Yours
The highest ratings in the batch went to modules very few sites run.
- Ffmpeg Image Toolkit. Highly critical, remote code execution. One site reports using it.
- Monster Menus. Critical, PHP object injection. Fourteen sites.
- Entity List. Critical, remote code execution, published October 14. Ninety sites.
- Custom Formatters. Critical, remote code execution, about 3,100 sites. It runs PHP code entered in the admin interface, so the risk sits with whoever holds administrator-level permissions. Fixed in 4.2.1.
The point. If one of these is on your site, it goes to the top of the list. If not, the severity rating is not a reason to panic. It is a reason to know what is installed, which is a ten-minute check most associations have never done.
What to Do This Week
- Update core first. Composer, or your host's update mechanism, to 11.4.10, 11.3.19 or 10.6.19. On Pantheon, the status page announced the Drupal 10 and 11 updates through Integrated Composer on October 15.
- Check your module list. Reports, then Available updates, lists every installed module and flags the ones with security releases. Compare it against this post.
- Test where it matters. Update on staging, click through member login, renewals, event registration and any AMS handoff, then deploy.
- And look at the calendar. Drupal 10's end of life on December 9 and PHP 8.2's on December 31 are both inside the next ten weeks. If a site needs this update and is on either, plan all three together.