Security

Drupal Security Updates for November 4 and 11: 48 Contrib Advisories, Ten Critical, and What to Update First

A two-color risograph print in pink and blue of a cobbler's workbench with a row of worn shoes, several freshly resoled and polished, a visual for Drupal security updates where many contributed modules need fixing at once

Two weeks of Drupal security updates brought 48 contributed module advisories, 24 on November 4 and 24 on November 11, 2026. Ten are rated Critical. The one Critical from November 11, in GraphQL Core Schema, can let a user change an administrator’s password.

This post follows our October 21 contrib advisories roundup and our post on the Drupal AI module advisories of October 28. It sorts both batches of Drupal security updates by what to update first, then lists the rest. Facts are as of November 15, 2026. Drupal posted no new core or contrib advisories between November 12 and November 15.

The short version: start your Drupal security updates with anything that needs no login. That means REST & JSON API Authentication, Workflow Notifications, Highlight Js and the commerce payment modules. Next, fix the account takeover bugs in GraphQL Core Schema, Simple OAuth and Authenticator Login Plus. Then work through the common modules: Smart Trim, Page Manager, COOKiES, Entity Print and Scheduler. Every Critical advisory marks the exploit as theoretical, so you have a short window, not none.

How we ordered these Drupal security updates

Drupal scores each advisory out of 25. Its risk level definitions put Critical at 15 to 19 and Moderately critical at 10 to 14. The score adds up factors such as how hard the attack is and what access the attacker needs. Our guide to reading a CVSS score covers the similar CVSS system.

We weigh one factor above the rest: whether an anonymous visitor can do it. Drupal calls that "A:None." A bug that needs an admin account matters less than one any visitor can reach. Then we weigh how common the module is on association and nonprofit builds.

The full list is on Drupal’s contributed project advisories page.

The ten Critical advisories

Module Advisory Risk (out of 25) Fixed in
REST & JSON API Authentication SA-CONTRIB-2026-298 17, no login 3.2.1
Content Synchronizer SA-CONTRIB-2026-293 17, code execution 4.1.1
GroupEx PRO (Daxko) SA-CONTRIB-2026-278 17, code execution 2.2.1
Workflow Notifications SA-CONTRIB-2026-297 16, no login 3.0.3
Highlight Js SA-CONTRIB-2026-299 16, no login 1.3.1
Commerce Product Alternative SA-CONTRIB-2026-301 16, no login 1.0.1
S3 File System CORS Upload SA-CONTRIB-2026-295 16 8.x-1.3
GraphQL Core Schema SA-CONTRIB-2026-316 15 1.0.29
Simple OAuth SA-CONTRIB-2026-296 15 5.2.6, 6.0.10, 6.1.4
Reset Password Email/SMS OTP SA-CONTRIB-2026-305 15, no login 1.0.5

All ten came out on November 4 except GraphQL Core Schema, which came out on November 11.

Update first: bugs any visitor can reach

REST & JSON API Authentication. The SA-CONTRIB-2026-298 advisory says the module "does not properly reject requests when an API key is unconfigured." That allows "unauthenticated attackers to bypass authentication and potentially access or modify protected resources." Sites are exposed when API authentication is on but no API key was generated. Update to 3.2.1. If you cannot, generate an API key now and check logs for odd admin access.

Workflow Notifications. Drupal says the module does not protect its Notification settings page, so an attacker can make changes without logging in. Update to 3.0.3.

Highlight Js. A reflected cross-site scripting (XSS) bug in its CKEditor 5 preview endpoint, open to anonymous users. Update to 1.3.1.

Commerce Product Alternative. Anonymous visitors could view other anonymous visitors’ carts, with product names and prices, and swap items. Carts of logged-in customers are not affected. Update to 1.0.1.

Payment webhooks. Two Moderately critical bugs also need no login. AlternativeCommerce PayPal Checkout let attackers mark an order as paid with a forged webhook (fixed in 1.1.1). Commerce Escrow let spoofed Escrow.com webhooks mark orders paid, completed or canceled. Commerce Escrow 1.1.0 fixes it, and you must then enter the new webhook URL at Escrow.com. If you run Drupal Commerce, also check our post on the exploited Commerce Core flaw.

Next: account takeover and admin access

GraphQL Core Schema. The SA-CONTRIB-2026-316 advisory (CVE-2026-126725) says "A user who can view another user’s account can change that account’s password, including on administrator accounts." Drupal adds, "This can lead to a full account takeover." Only GraphQL servers with the User Login schema extension turned on are exposed. Update to 1.0.29. The stopgap is to turn off that extension, but that also removes the login and password mutations a decoupled front end may use. Our explainer on headless CMS covers why GraphQL shows up on these builds.

Simple OAuth (OAuth2) & OpenID Connect. The SA-CONTRIB-2026-296 advisory says users who can create or edit consumers can set up malicious ones and get tokens with more access. That can reach "full administrative access." The attacker needs the "Add consumer entities" or "Update own consumer entities" permission. Update to 6.1.4, 6.0.10 or 5.2.6, depending on your branch. Two follow-up steps matter:

  • Grant the new Administer consumer access settings permission only to trusted roles.
  • On 6.1.x, Client Credentials tokens are now always limited to their scopes. Existing consumers are not changed, so review them and revoke their tokens if in doubt.

Two-factor and password bugs

Authenticator Login Plus (2FA). Three Moderately critical bypasses, all fixed in 1.0.3:

  • SA-CONTRIB-2026-320: someone who knows a password can skip the second factor on routes that use a per-request login method, such as HTTP Basic Authentication with REST or JSON:API.
  • SA-CONTRIB-2026-321: someone with only the first factor can trigger login actions, such as updating the last login time.
  • SA-CONTRIB-2026-322: under some conditions, an attacker can take over a 2FA account. They need their own account, control of the victim’s email or password, and a won race.

Our explainer on authenticator apps covers how the second factor works.

Password reset and change. Reset Password Email/SMS OTP did not block resets for blocked users (fixed in 1.0.5). Drupal notes an admin must still unblock the user first. Password Separate Form had weak current-password checks (fixed in 2.0.3).

Code execution bugs that need an account

Content Synchronizer. A crafted import file can lead to remote code execution, according to SA-CONTRIB-2026-293. A second advisory, SA-CONTRIB-2026-294, is an XSS bug. Both are fixed in 4.1.1. The attacker needs admin-level access.

GroupEx PRO (Daxko) integration. SA-CONTRIB-2026-278 is a PHP object injection bug that could lead to code execution. The Drupal Security Team marked the project unsupported on October 28 and restored it on November 4, when 2.2.1 shipped. Update to 2.2.1.

Drupal security updates for common association and nonprofit modules

These are Moderately critical, but they are on many builds.

  • Smart Trim: XSS through its Twig filter. Sites that use only the field formatter are not exposed. Fixed in 2.3.2 and 2.2.2.

  • Page Manager: cross-site request forgery in the Page Manager UI submodule, against users with "administer pages." Update to 8.x-4.1, then run database updates or clear caches. Or uninstall the UI submodule on production. Existing pages keep working.

  • COOKiES Consent Management: XSS in how the COOKiES Video submodule handles Blazy iframes. Needs admin-level access. Fixed in 1.2.17.

  • Entity Print: when printing pages with outside images or stylesheets, it sent the user’s session cookie to those hosts. An attacker needs a text format, such as Full HTML, that allows them. Update to 8.x-2.20, or turn off Dompdf’s "Enable Remote URLs."

  • Scheduler: editors could change publish dates they should not, through JSON:API or REST. Fixed in 1.7.0, 2.2.3 and 2.3.1. The 2.1.x branch is unsupported.

  • Paragraphs Edit (3.0.2) and Paragraphs entity embed (4.0.1): weak access checks and XSS.

The rest of the November Drupal security updates

Module Issue Risk Fixed in
Layout Builder iFrame Modal XSS 13 1.3.9, plus core 10.5.9, 10.6.7, 11.2.11 or 11.3.7
Mollie for Drupal (2) Webhook check; token leak 13, 13 2.3.2
Commerce License (2) Access bypass 13, 9 3.1.2
Commerce sermepa Improper authorization 13 8.x-2.5
File Resumable Upload Improper authorization 13 2.0.6
Download Count Access bypass 13 2.2.5, 3.0.2
AdobeAnalytics XSS 13 8.x-1.1
Texts (2) XSS; CSRF 14, 11 1.0.17
Extended HTML Filter XSS 14 1.0.4
htmLawed (2) XSS 14, 11 4.1.11, 8.x-3.10
Data field XSS 12 2.0.15, 3.0.1
Campaign Monitor CSRF 12 3.0.3
Name Field XSS 12 8.x-1.6
WordsOnline Connector SQL injection 12 2.0.6
S3 File System CORS Upload Improper authorization 11 8.x-1.4
Real Name Twig injection 10 2.0.1
Islandora File overwrite 10 2.19.1
Mime Mail Information disclosure 10 2.0.4
Forum Access Access bypass 10 2.0.3
Allowed Languages Access bypass 7 2.0.3

S3 File System CORS Upload had a Critical fix on November 4 and a second fix on November 11, so move straight to 8.x-1.4.

Drupal security updates and Drupal 10

Drupal’s core release schedule sets the monthly core security window for the third Wednesday. The next one is November 18. Drupal’s schedule also says 10.6.x is the last Drupal 10 minor. Since Drupal cut minor-version support to eight months, staying current on core matters more, as our post on the new support rule explains.

Drupal 10 reaches end of life on December 9, 2026. After that date, Drupal 10 core gets no more security releases, so future Drupal security updates for core will target Drupal 11 and later. See our Drupal 10 end-of-life guide and our plain-language guide to the Webform advisories for what to check now.

If your Drupal sites run on Apache, the server needs a patch too. See our post on the Apache HTTP/2 vulnerability.

How to apply these Drupal security updates

  1. List what you run. On each site, run composer show "drupal/*" and compare against the tables.
  2. Update with Composer. For example, composer update drupal/simple_oauth --with-dependencies.
  3. Run database updates with drush updb, then clear caches. Page Manager needs this step.
  4. Do the follow-ups. Simple OAuth permissions and tokens, the Escrow.com webhook URL, and the REST API key.
  5. Check logs on sites that ran the no-login modules for odd admin activity.

Frequently Asked Questions

How many Drupal security updates came out on November 4 and 11?

48 contributed project advisories, 24 each day. Ten are rated Critical, 36 Moderately critical and two Less critical.

Which advisory should I patch first?

Any you run that needs no login, starting with REST & JSON API Authentication (17 out of 25). Then GraphQL Core Schema and Simple OAuth, which can lead to account takeover.

Are any of these being exploited?

All ten Critical advisories mark the exploit as theoretical. In Drupal’s terms, no public exploit code or documentation exists. That can change after release.

Is my GraphQL site affected?

Only if it uses GraphQL Core Schema before 1.0.29 with the User Login schema extension turned on. Update to 1.0.29.

What changed in Simple OAuth?

A new permission, Administer consumer access settings, controls what access a consumer grants. On 6.1.x, Client Credentials tokens are always limited to their scopes. Review existing consumers.

We use Smart Trim. Are we exposed?

Only if your templates use its Twig filters. The field formatter alone is not affected. Update to 2.3.2 or 2.2.2 anyway.

Did Drupal publish anything after November 11?

Not as of November 15, 2026. The next core security window is November 18.

Do these Drupal security updates work on Drupal 10?

Most do today. Layout Builder iFrame Modal also needs core 10.5.9, 10.6.7 or later. Drupal 10 itself ends on December 9, 2026.

Where can I see every advisory?

On Drupal’s contributed project advisories page at drupal.org/security/contrib. Each advisory lists affected and fixed versions.

Digital Matters

Security Desk