INTEREST JOURNAL DRUPAL & WEB

Drupal Security Updates: October 29, 2026

About 2,600 words 12 min read

Japanese ↗
On this page

I read the Security-news notifications from Drupal.org to check for module updates and security measures relevant to my sites. Translating and checking each English notification takes time, so I have organized this week’s information by module.

This article covers all 39 advisories dated October 28, 2026 on Drupal’s official list of contributed-project security advisories ↗ . The article is dated October 29, when I reviewed the notifications in Japan. It does not summarize Drupal core updates.

I have grouped multiple advisories for the same module together while keeping each advisory ID. The fixed versions below are those specified in these advisories. Before updating, check the latest official guidance, your installed release branch, and its Drupal compatibility.

What to check first

Commerce Core advisory SA-CONTRIB-2026-254 concerns a vulnerability already being exploited on live sites. The official guidance calls for updating affected versions and checking orders for inconsistencies. Official advisory: SA-CONTRIB-2026-254 ↗

Three projects—CacheFlush, PayUmoney for Drupal Commerce, and GroupEx PRO ( Daxko ) integration—have been marked unsupported because known security issues remain unfixed. The recommendation is to uninstall them, which requires a different response from installing a fixed release.

I use the official English severity labels and scores out of 25. The 39 advisories comprise one Highly critical, 11 Critical, 24 Moderately critical, and three Less critical issues. Consider your actual configuration and the conditions required for exploitation alongside the severity rating.

If a table does not fit on your screen, scroll horizontally within it.

Commerce modules

Commerce Core: six advisories

Machine name: commerce. The common update targets are 3.3.13 for 3.x and 8.x-2.41 for 8.x-2.x. The affected version ranges differ by advisory; notably, advisory 255 explicitly excludes 3.3.x.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-254 ↗
CVE-2026-118539
Highly critical 21/25 Inadequate access checks on routes and entity fields may cause financial harm to vendors. Exploitation on live sites has been confirmed.
SA-CONTRIB-2026-255 ↗
CVE-2026-118540
Moderately critical 12/25 JSON:API may expose unpublished product variations without permission when published products have unpublished variations. The 3.3.x branch is not affected by this issue.
SA-CONTRIB-2026-256 ↗
CVE-2026-118541
Less critical 9/25 Users restricted to managing their own promotions may modify or remove coupons belonging to other promotions. The site must accept writes through JSON:API or REST.
SA-CONTRIB-2026-257 ↗
CVE-2026-118542
Moderately critical 10/25 Users permitted to create stores or edit their own store may make it the default and receive orders intended for others. This affects configurations granting those permissions to untrusted users.
SA-CONTRIB-2026-258 ↗
CVE-2026-118543
Moderately critical 12/25 CSRF may let an attacker trick an administrator into dismissing shared announcements, hiding security update notices from other administrators as well.
SA-CONTRIB-2026-259 ↗
CVE-2026-118544
Moderately critical 11/25 Repeated JSON:API requests may reveal particular field values on unpublished variations, including variations of unpublished products.

For advisory 254, audit orders for inconsistencies as well as updating. A successful update does not establish that no unauthorized activity occurred earlier.

Commerce Stripe: three advisories

Machine name: commerce_stripe. Update 2.x installations to 2.2.3. The official guidance also directs users of the unsupported 2.0.x and 2.1.x branches to 2.2.3.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-263 ↗
CVE-2026-118558
Critical 15/25 Missing CSRF protection in the Stripe Connect authorization flow may let an attacker trick an administrator into marking an order paid without payment. This issue does not affect 8.x-1.x.
SA-CONTRIB-2026-264 ↗
CVE-2026-118559
Moderately critical 12/25 Webhook signatures are inadequately checked when the payment gateway’s signing secret is not properly configured. Installations on 8.x-1.3 or earlier should update to 8.x-1.4.
SA-CONTRIB-2026-265 ↗
CVE-2026-118560
Moderately critical 11/25 XSS under particular conditions involving payment gateway administration permissions, Stripe Connect, and a compromised external service. This issue does not affect 8.x-1.x.

Commerce Shipping: two advisories

Machine name: commerce_shipping. Update 3.0.x to 3.0.6, or 8.x-2.x to 8.x-2.16.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-261 ↗
CVE-2026-118556
Moderately critical 11/25 Insufficient protection of shipment references and fields may allow unauthorized shipment state changes or deletion. The attacker must have a cart with API access to its shipments.
SA-CONTRIB-2026-262 ↗
CVE-2026-118557
Less critical 8/25 Access checks on the receipt resend form may expose receipts and customer details for orders a user is not permitted to access, depending on the configuration.

Commerce License: one advisory

SA-CONTRIB-2026-260 ↗
CVE-2026-118555 — Moderately critical 12/25. Machine name: commerce_license. Update to 3.1.1.

A license owner with the update own commerce_license permission may change the rights and state of the license, potentially escalating privileges as far as the Administrator role. That permission is not granted by default.

For sites that granted it, the official guidance also calls for checking role licenses for unexpected roles and reviewing which users have administrative roles.

AI modules: eight advisories

Machine name: ai. Update 1.5.x to 1.5.2, or 1.4.x to 1.4.11. The 1.3.x branch is unsupported and must be moved to one of these supported branches.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-266 ↗
CVE-2026-118545
Moderately critical 14/25 Inadequate HTML rendering restrictions may cause XSS. The attacker needs access to a text format capable of rendering HTML.
SA-CONTRIB-2026-267 ↗
CVE-2026-118546
Moderately critical 13/25 In certain AI Chatbot configurations, user input is inadequately filtered before rendering, allowing XSS. The attacker needs block administration access.
SA-CONTRIB-2026-268 ↗
CVE-2026-118548
Moderately critical 11/25 Inadequate link validation may allow sensitive information to leave the site. Exploitation involves untrusted sources used in AI interactions that produce rendered HTML.
SA-CONTRIB-2026-269 ↗
CVE-2026-118549
Critical 15/25 Incomplete validation of Markdown links under certain conditions may allow XSS.
SA-CONTRIB-2026-270 ↗
CVE-2026-118550
Moderately critical 10/25 AI Search result caching may expose titles and other displayed fields from restricted or unpublished content. See below for the configuration conditions and standalone module fixes.
SA-CONTRIB-2026-271 ↗
CVE-2026-118551
Less critical 8/25 Transcription audio left in the temporary directory may be read by others. The attacker must be able to read that directory.
SA-CONTRIB-2026-272 ↗
CVE-2026-118552
Moderately critical 14/25 Inadequate sanitization of some HTMX attributes may allow XSS.
SA-CONTRIB-2026-273 ↗
CVE-2026-118553
Moderately critical 11/25 AI Automator does not adequately check text format permissions, allowing field input in formats the user should not be permitted to use and potentially causing XSS.

Check how AI Search is installed

Advisory 270 applies when AI Search is used with a Search API View, Search API result caching is enabled, and the same search performed by an authorized user remains cached. The default Search API (none) setting is unaffected. RAG tools, AI Assistant RAG actions, and custom code making Search API queries directly are also outside the affected scope described in the advisory.

The standalone AI Search module is affected too, alongside the submodule bundled with AI. The official update targets for the standalone module are 1.3.0-alpha6 for 1.3.x and 2.0.0-alpha3 for 2.0.x. Updating AI itself does not establish that a separately installed AI Search module has also been updated. The bundled AI Search submodule is deprecated, and the advisory suggests considering migration to the standalone module. Official advisory: 270 ↗

For advisory 271, the fix processes audio in memory. The official guidance also suggests considering removal of any speech_to_text.mp3 file left in the temporary directory. Official advisory: 271 ↗

Synchronization and files

Single Content Sync: two advisories

Machine name: single_content_sync. Update to 1.4.19.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-274 ↗
CVE-2026-118561
Critical 17/25 Inadequate validation of import sources and destinations may allow arbitrary file writes, local file disclosure, or requests to internal and external systems. RCE may also be possible depending on server configuration.
SA-CONTRIB-2026-275 ↗
CVE-2026-118562
Critical 17/25 Deserializing data from a malicious import file may lead to remote code execution.

Both require the import single content permission for exploitation. Advisory 274 calls for database updates and cache rebuilding after upgrading, together with a review ensuring that this permission is granted only to highly trusted roles.

Remote file retrieval during imports becomes disabled by default. Sites that need it must configure trusted file hosts or consider importing ZIP files containing the required assets. Official advisory: 274 ↗

Content Sync (content-sync.io): one advisory

SA-CONTRIB-2026-291 ↗
CVE-2026-118568 — Moderately critical 12/25. Machine name: cms_content_sync. Update to 3.2.2.

Inadequate encryption of the synchronization system user’s password may allow it to be read. The attacker must already have a database dump or read access to the user data table; the advisory states that prior database access is required for exploitation.

Stage File Proxy: one advisory

SA-CONTRIB-2026-286 ↗
CVE-2026-118576 — Critical 16/25. Machine name: stage_file_proxy. Update to 4.0.1 or 3.1.7.

Incomplete file URL validation during fallback retrieval may allow XSS. The module must be enabled on the target, and the attacker must be able to upload a malicious file to its configured origin server. The official advisory emphasizes that this is a development module and is not intended for production sites.

S3 File System: one advisory

SA-CONTRIB-2026-279 ↗
CVE-2026-118574 — Moderately critical 14/25. Machine name: s3fs. Update to 8.x-3.12.

Insufficient separation of upload state across multiple file operations within one request may apply incorrect ACLs or unintended operation metadata.

If the site takes over private:// storage through S3 without enabling s3fs.upload_as_private, audit private objects for public-read ACLs. If any are found, review S3 access logs where available. Sites using S3FS hooks should also check that customizations apply only to the intended objects. Consult the official advisory for configuration-dependent exposure and access controls during the audit.

Media Alias Display: one advisory

SA-CONTRIB-2026-292 ↗
CVE-2026-118571 — Moderately critical 11/25. Machine name: media_alias_display. Update 3.0.x to 3.0.3, or 2.1.x to 2.1.3.

Files that should remain uncacheable may receive public cache headers, allowing another user to receive a cached copy previously requested by a more privileged user. Conditions include handling non-public files through an additional file scheme. This follows SA-CONTRIB-2026-245, which did not fully resolve the issue.

Authentication and permissions

OAuth Login - OAuth OIDC SSO: one advisory

SA-CONTRIB-2026-284 ↗
CVE-2026-118572 — Critical 15/25. Machine name: oauth_login_oauth2. Update to 3.1.1.

Insufficient configuration route access checks and insufficient verification of the email address returned by the identity provider may let an attacker log in as an existing user whose email address they know. The attacker needs an account with a provider configured on the site and must control at least one returned attribute.

OAuth2 Token Manager: one advisory

SA-CONTRIB-2026-290 ↗
CVE-2026-118573 — Critical 15/25. Machine name: oauth2_token_manager. Update to 8.x-1.2.

Inadequate OAuth2 route restrictions may allow an anonymous user to connect a site’s external integration to an attacker-controlled account. The attacker must obtain the OAuth2 state value from an earlier system token initialization, for example through access logs.

Run database updates after upgrading. If you suspect that a Box, Quip, or Slack integration was connected to an unauthorized account, the official guidance calls for reinitializing the system token through Drush. It does not require token reinitialization on every site.

OpenID Connect Client: one advisory

SA-CONTRIB-2026-287 ↗
CVE-2026-118554 — Moderately critical 14/25. Machine name: oidc. Update to 2.3.1.

Automatic linking of a new login to an existing account with the same email address may allow account takeover. This requires a provider that does not verify email addresses and affects accounts not yet linked to an OpenID Connect user. User 1 is excluded.

The update disables automatic linking to existing accounts by default. Review the settings before re-enabling it. For a generic realm, configuring the claim indicating a verified email address is also strongly recommended.

Field Permissions: two advisories

Machine name: field_permissions. Update to 8.x-1.6.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-288 ↗
CVE-2026-118583
Moderately critical 11/25 A role whose machine name is administrator, but which is not designated as the site’s administrator role, may bypass field restrictions. Drupal’s default administrator role configuration is unaffected.
SA-CONTRIB-2026-289 ↗
CVE-2026-118584
Moderately critical 13/25 Private fields on entity types without an owner or author are not adequately protected. The attacker must already be able to view the entity. Custom permissions and Private fields on entity types with an owner are unaffected.

Bulk Update User Roles: one advisory

SA-CONTRIB-2026-280 ↗
CVE-2026-118567 — Moderately critical 12/25. Machine name: bulk_update_user_roles. Update to 1.0.5.

Insufficient access checks on the bulk role update form may allow users without role assignment permission to perform the operation. The attacker must have the administer users permission.

Content controls and forms

Fasttoggle: two advisories

Machine name: fasttoggle. Update to 4.1.1.

Official advisory Severity Issue and main conditions
SA-CONTRIB-2026-282 ↗
CVE-2026-118569
Moderately critical 13/25 Inadequate checks on the target entity may allow publication status changes to content the user cannot view or update. The attacker needs the Use Fasttoggle permission.
SA-CONTRIB-2026-283 ↗
CVE-2026-118570
Moderately critical 13/25 Missing CSRF protection on toggle URLs may allow unauthorized actions if a logged-in user with Use Fasttoggle permission is tricked into visiting an attacker-controlled page.

CAPTCHA: one advisory

SA-CONTRIB-2026-281 ↗
CVE-2026-118582 — Moderately critical 13/25. Machine name: captcha. Update 2.0.x to 2.0.11, or 8.x-1.x to 8.x-1.18.

A solved CAPTCHA session is not fully invalidated, allowing a previously submitted form to be submitted again without solving a new challenge. This weakens defenses against spam submissions and repeated login attempts. The advisory follows the earlier fix in SA-CONTRIB-2026-015.

Signature pad widget: one advisory

SA-CONTRIB-2026-285 ↗
CVE-2026-118575 — Critical 16/25. Machine name: sign_widget. Update to 8.x-1.15.

User-supplied signature content is inadequately sanitized before it is saved as an SVG image in public storage. Under certain conditions, a crafted file may cause XSS.

Unsupported projects: three uninstall recommendations

The following projects have been marked unsupported because known security issues remain unfixed. All three are rated Critical 16/25, affect all versions, and carry an official recommendation to uninstall the project.

Official advisory Project Machine name
SA-CONTRIB-2026-276 ↗
CVE-2026-118563
CacheFlush cacheflush
SA-CONTRIB-2026-277 ↗
CVE-2026-118564
PayUmoney for Drupal Commerce commerce_payumoney
SA-CONTRIB-2026-278 ↗
CVE-2026-118565
GroupEx PRO ( Daxko ) integration groupexpro

Review the impact on the features and data your site uses, and prepare a replacement where necessary.

Administrator checklist

  1. Check what is installed and enabled. Review Composer-managed packages and enabled modules and submodules, including development modules and standalone AI Search.
  2. Compare against the official advisories. Check each installed version against Affected versions, then review permission, API, caching, and authentication conditions. Different advisories for the same module may have different conditions.
  3. Back up and prepare a recovery plan before updating. Preserve code, the database, and required files. Check dependencies and compatibility, test the update in a verification environment, and then deploy to production.
  4. Complete the follow-up checks. Alongside required database updates and cache rebuilding, review orders, license roles, S3 ACLs, and Single Content Sync permissions and file sources as directed by each advisory.
  5. Record the outcome. Keep a record of installed versions, test results, and follow-up findings. Preserve relevant logs for investigation if unauthorized activity is suspected.

Example command to inspect installed packages:

composer show "drupal/*"

Example command to inspect enabled modules, where the project includes Drush:

vendor/bin/drush pm:list --type=module --status=enabled

These commands inspect the installation. Choose actual update commands according to the site’s Composer configuration and dependencies.

Closing thoughts

I check the Drupal.org Security-news messages that arrive early on Thursday mornings in Japan and use them to guide Drupal updates and security maintenance.

Translating the English notifications and comparing them against installed modules takes time, particularly in weeks with many advisories. I put this article together because grouping the information by module makes the required work easier to review.

This article is an aid to reading the official information. My summaries or interpretations may contain errors, so always follow the links to check the latest details and assess how they apply to your own site before taking action.

Drupal Guide ↗