Newsfeed-Generator
S3 File System - Moderately critical - Access bypass - SA-CONTRIB-2026-279
S3 File System (s3fs) provides an additional file system to your Drupal site that stores files in Amazon's Simple Storage Service (S3) storage.
The module doesn't sufficiently isolate upload context between separate object(file) operations in the same request resulting in the potential for objects to be uploaded with incorrect access control list (ACL) entries or corruption through incorrect operation metadata.
This vulnerability is mitigated by the fact that an attacker must be able to trigger multiple file operations on S3FS.
Some vectors are mitigated by:
- Not enabling private:// takeover ($settings['s3fs.use_s3_for_private'] = FALSE;) or only enabled with $settings['s3fs.upload_as_private'] = TRUE;
- The deployment does not utilize hook_s3fs_stream_open_params_alter(), hook_s3fs_upload_params_alter(), hook_s3fs_copy_params_alter(), or hook_s3fs_command_params_alter()
If both points above have always been true, all currently known vectors are mitigated.
Solution:Install the latest version:
- If you use the S3 File System module for Drupal 8.x, upgrade to s3fs 8.x-3.12
If private:// takeover is enabled without $settings['s3fs.upload_as_private'] = TRUE; audit all private object ACL's to ensure no objects include a public read ACL entry. If private objects with public read ACL are discovered, audit S3 Bucket Access logs (if enabled).
If using S3FS hooks, audit all objects to ensure any applied customization is reflected only on the intended objects.
While auditing objects, site owners may disable ACLs and utilize a Bucket Access Policy to block public access to private:// files. See the s3fs 8.x-3.12 README.txt for a sample policy. $settings['s3fs.use_s3_for_private'] = TRUE; must be configured prior to disabling ACLs.
Note: With ACLs disabled, the S3 getObjectAcl call will not report ACL entries. If this feature is enabled, consider utilizing an AWS S3 Inventory report to obtain object metadata.
Reported By: Fixed By: Coordinated By:- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
Fasttoggle - Moderately critical - Cross-Site Request Forgery - SA-CONTRIB-2026-283
This module enables you to quickly toggle the publication status, promotion and stickiness of nodes, and the publication status of comments, from links on the page.
The module doesn't sufficiently protect against cross-site request forgery (CSRF) on its toggle URL, under the scenario where a user with the "Use Fasttoggle" permission visits a page controlled by an attacker while logged in. This allows the attacker to change the publication status of arbitrary content on behalf of that user.
This vulnerability is mitigated by the fact that an attacker must trick a user with the permission "Use Fasttoggle" into visiting an attacker-controlled page.
Solution:Install the latest version:
- If you use the Fasttoggle module, upgrade to Fasttoggle 4.1.1
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
Fasttoggle - Moderately critical - Access bypass - SA-CONTRIB-2026-282
This module enables you to quickly toggle the publication status, promotion and stickiness of nodes, and the publication status of comments, from links on the page.
The module doesn't sufficiently check access to the entity being toggled, under the scenario where a user with the "Use Fasttoggle" permission submits a request to the toggle URL for any node or comment regardless of their permission to update that entity. For example, such a user could publish an unpublished draft they are not allowed to view.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Use Fasttoggle".
Solution:Install the latest version:
- If you use the Fasttoggle module, upgrade to Fasttoggle 4.1.1
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
CAPTCHA - Moderately critical - Session Replay (CAPTCHA bypass) - SA-CONTRIB-2026-281
The CAPTCHA module places a configurable challenge on forms to block automated submissions. To skip the challenge on later steps of the same multi-step form, the module remembers that a CAPTCHA session has been solved.
The module does not fully invalidate a solved CAPTCHA session. As a result, a protected form that was already submitted once can be submitted again without solving a new CAPTCHA. This weakens the protection the module provides against automated submissions such as spam registrations, comment spam, and login brute-forcing.
This is a follow-up to the earlier CAPTCHA replay fix (SA-CONTRIB-2026-015 / CVE-2026-3214), which closed one replay path but left this one open.
Solution:Install the latest version:
- If you use the Captcha module 2.0.x, upgrade to Captcha 2.0.11.
- If you use the Captcha module 8.x-1.x, upgrade to Captcha 8.x-1.18.
- James Gilliland (neclimdul) of the Drupal Security Team
- Rodrigo Cabo (rodrigo-cabo)
- Jakob P (japerry)
- James Gilliland (neclimdul) of the Drupal Security Team
- Rob Loach (robloach)
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Damien McKenna (damienmckenna) of the Drupal Security Team
- Michael Hess (mlhess) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Pierre Rudloff (prudloff) of the Drupal Security Team
- Stella Power (stella) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
PayUmoney for Drupal Commerce - Critical - Unsupported - SA-CONTRIB-2026-277
The Drupal Security Team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, read the documentation on becoming the maintainer of a project that is unsupported for security reasons.
Solution:If you use this project, you should uninstall it.
To take over maintainership, read Becoming the maintainer of a project that is unsupported for security reasons.
Reported By:- Drew Webber (mcdruid) of the Drupal Security Team
- Swan Kalata (akalata) of the Drupal Security Team
- Drew Webber (mcdruid) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
CacheFlush - Critical - Unsupported - SA-CONTRIB-2026-276
The Drupal Security Team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, read the documentation on becoming the maintainer of a project that is unsupported for security reasons.
Solution:If you use this project, you should uninstall it.
To take over maintainership, read Becoming the maintainer of a project that is unsupported for security reasons.
Reported By:- Ivo Van Geertruyen (mr.baileys) of the Drupal Security Team
- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Ivo Van Geertruyen (mr.baileys) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Pierre Rudloff (prudloff) of the Drupal Security Team
Single Content Sync - Critical - Remote code execution - SA-CONTRIB-2026-275
Single Content Sync enables exporting and importing content, referenced entities, and files between Drupal sites.
A maliciously crafted import file can cause untrusted data to be deserialized, potentially leading to remote code execution.
This vulnerability is mitigated by the fact that an attacker must have a role with the "import single content" permission.
Solution:Install the latest version:
- Upgrade to Single Content Sync 1.4.19.
- Drew Webber (mcdruid) of the Drupal Security Team
- Drew Webber (mcdruid) of the Drupal Security Team
- Oleksandr Kuzava (nginex)
- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Lee Rowlands (larowlan) of the Drupal Security Team
- Drew Webber (mcdruid) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
Single Content Sync - Critical - External control of file name or path - SA-CONTRIB-2026-274
Single Content Sync enables exporting and importing content, referenced entities, and files between Drupal sites.
The module does not sufficiently validate file sources and destinations during content imports. An attacker can write arbitrary files, disclose sensitive local files accessible to the web server, or cause the server to make requests to internal or external resources. Depending on the server configuration, this may lead to remote code execution.
Exploitation requires the import single content permission. This permission is marked as restricted starting with version 1.4.18. Remote code execution additionally depends on the server permitting execution of attacker-controlled files.
Solution:Install the latest version:
- If you use the Single Content Sync module, upgrade to Single Content Sync 1.4.19.
Run database updates and rebuild caches after upgrading. Review the module permissions and ensure only highly trusted roles have the "import single content" permission.
Remote file downloads during imports are disabled by default. Sites that require this functionality must configure trusted file hosts in the module settings. Alternatively, import ZIP files containing the required assets.
Reported By: Fixed By: Coordinated By:- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-273
The AI module includes a submodule, AI Automator. This submodule allows you to automatically fill out fields using AI, based on other fields.
The module doesn't sufficiently check access to text formats, allowing users to author field data in text formats they should not have access to.
Solution:Install the latest version:
- If you use the AI module 1.5.x, upgrade to AI 1.5.2.
- If you use the AI module 1.4.x, upgrade to AI 1.4.11.
- If you use the AI module 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- Artem Dmitriiev (a.dmitriiev)
- Abhisek Mazumdar (abhisekmazumdar)
- Ahmad Khader (ahmad khader)
- Marcus Johansson (marcus_johansson)
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-272
This module provides a framework for integrating AI providers and features into Drupal.
The module doesn't sufficiently sanitize certain HTMX attributes, which can lead to a cross-site scripting (XSS) vulnerability.
Solution:Install the latest version:
- If you use version 1.5.x, upgrade to AI 1.5.2.
- If you use version 1.4.x, upgrade to AI 1.4.11.
- If you use version 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- Pierre Rudloff (prudloff) of the Drupal Security Team
- Artem Dmitriiev (a.dmitriiev)
- Ahmad Khader (ahmad khader)
- Marcus Johansson (marcus_johansson)
- Valery Lourie (valthebald)
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Less critical - Information Disclosure - SA-CONTRIB-2026-271
This module provides a framework for integrating AI providers and features into Drupal.
Audio for every speech-to-text request is written to the same file in the temporary directory and does not delete it afterwards. As a result, an attacker who can read the site's temporary directory could get the audio that another user sent for transcription.
This vulnerability is mitigated by the fact that the attacker needs read access to the temporary directory, either through the server (for example a shared hosting account) or through a module or custom code that exposes temporary files to other users. Drupal core's system.temporary route only serves temporary files to the user who owns them.
Solution:Install the latest version:
- If you use version 1.5.x, upgrade to AI 1.5.2.
- If you use version 1.4.x, upgrade to AI 1.4.11.
- If you use version 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
The fix keeps the audio in memory and no longer writes it to the temporary directory. Site owners may also want to delete any leftover speech_to_text.mp3 file in the temporary directory.
Reported By: Fixed By: Coordinated By:- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Moderately critical - Access bypass - SA-CONTRIB-2026-270
This module provides a framework for integrating Drupal with AI providers. Its AI Search submodule provides a Search API backend that stores content in a vector database for semantic search.
The AI Search submodule has always been marked as 'experimental' but more importantly is deprecated. You may wish to use this as an opportunity to move to the standalone AI Search which is a drop-in replacement and target of all new development. It also had the same vulnerability.
The AI Search backend checks access to each search result for the current user, but this is not taken into account when Search API caches the results of a view. As a result, cached search results, including titles and other displayed fields of unpublished or access-restricted content, can be shown to users who do not have access to that content in some configurations.
This vulnerability is mitigated by the fact that:
- The AI Search submodule must be enabled and used with a Search API view.
- The view must use Search API result caching ("Search API (time-based)", "Search API (tag-based)" or "Search API (time and tag-based)"). The default, "Search API (none)", is not affected.
- A user with access to the restricted content must have run the same search within the cache lifetime.
Retrieval-augmented generation (RAG) tools, AI Assistant RAG actions and custom code running Search API queries are not affected.
Solution:Install the latest version:
- If you use the AI module 1.5.x with the AI Search submodule, upgrade to AI 1.5.2
- If you use the AI module 1.4.x with the AI Search submodule, upgrade to AI 1.4.11
- If you use the AI module 1.3.x with the AI Search submodule, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- If you use the AI Search 1.3.x standalone module, upgrade to AI 1.3.0-alpha6
- If you use the AI Search 2.0.x standalone module, upgrade to AI 2.0.0-alpha3
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
AI (Artificial Intelligence) - Critical - Cross-site scripting - SA-CONTRIB-2026-269
This AI module enables you to interact with AI providers. It has a service that helps any consumer of the module to stop cross site scripting elements from appearing.
The module does not sufficiently validate Markdown links under certain conditions, potentially allowing cross-site scripting (XSS).
Solution:Install the latest version:
- If you use version 1.5.x, upgrade to AI 1.5.2.
- If you use version 1.4.x, upgrade to AI 1.4.11
- If you use version 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- Artem Dmitriiev (a.dmitriiev)
- Abhisek Mazumdar (abhisekmazumdar)
- Ahmad Khader (ahmad khader)
- Marcus Johansson (marcus_johansson)
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Moderately critical - Information disclosure - SA-CONTRIB-2026-268
This module enables you to use AI on the website. It also enables you to interact with AI providers.
The module does not sufficiently validate links under certain conditions, potentially allowing the exfiltration of sensitive information to external sites.
This vulnerability is mitigated by the fact that an attacker must use untrusted sources when interacting with the AI module in a way that produces rendered HTML.
Solution:Install the latest version:
- If you use version 1.5.x, upgrade to AI 1.5.2
- If you use version 1.4.x, upgrade to AI 1.4.11
- If you use version 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-267
This module enables you to use AI on the website. It includes an AI Chatbot submodule allows you to setup a chatbot.
Under certain configurations, the chatbot does not sufficiently filter user input before rendering it, potentially allowing cross-site scripting (XSS).
This vulnerability is mitigated by the fact that an attacker must have access to administer blocks.
Solution:Install the latest version:
- If you use version 1.5.x, upgrade to AI 1.5.2.
- If you use version 1.4.x, upgrade to AI 1.4.11.
- If you use version 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- Artem Dmitriiev (a.dmitriiev)
- Abhisek Mazumdar (abhisekmazumdar)
- Ahmad Khader (ahmad khader)
- Marcus Johansson (marcus_johansson)
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
AI (Artificial Intelligence) - Moderately critical - Cross-site scripting - SA-CONTRIB-2026-266
This module enables you to use AI on the website.
The module does not sufficiently restrict HTML rendering, allowing cross-site scripting (XSS) under certain conditions.
This vulnerability is mitigated by the fact that an attacker must have access to a text format that can render HTML.
Solution:Install the latest version:
- If you use the AI module 1.5.x, upgrade to AI 1.5.2
- If you use the AI module 1.4.x, upgrade to AI 1.4.11
- If you use the AI module 1.3.x, upgrade to AI 1.5.2 or AI 1.4.11 as the 1.3.x branch is now unsupported.
- Artem Dmitriiev (a.dmitriiev)
- Abhisek Mazumdar (abhisekmazumdar)
- Ahmad Khader (ahmad khader)
- Marcus Johansson (marcus_johansson)
- Swan Kalata (akalata) of the Drupal Security Team
- Bram Driesen (bramdriesen) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
Commerce Stripe - Moderately critical - Cross site scripting - SA-CONTRIB-2026-265
This module enables you to use the Stripe Connect API to quickly configure your Drupal Commerce store to take payments via multiple Stripe APIs.
Under certain rare circumstances, the module may expose a cross-site scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have administrator permissions to configure payment gateways and use the Stripe Connect in conjunction with the compromise of an external service.
Solution:Install the latest version:
- Upgrade to Commerce Stripe 2.2.3.
- Commerce Stripe 2.0.x and 2.1.x are no longer supported, so sites on older versions should also update to Commerce Stripe 2.2.3.
- Commerce Stripe 8.x-1.x is not affected.
- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
Commerce Stripe - Moderately critical - Improper verification of cryptographic signature - SA-CONTRIB-2026-264
This module enables you to take payments via multiple Stripe APIs.
The module doesn't sufficiently verify the cryptographic signature of a webhook event when a signing secret has not been properly configured in the payment gateway settings.
This vulnerability is mitigated by the fact that not all payment gateway plugins in the module utilize webhooks. Furthermore, any payment gateway configuration with any value for its webhook signing secret will prevent inappropriate processing.
Solution:Install the latest version:
- Upgrade to Commerce Stripe 2.2.3.
- Commerce Stripe 2.0.x and 2.1.x are no longer supported, so sites on older versions should also update to Commerce Stripe 2.2.3.
- If you use Commerce Stripe 8.x-1.3 or earlier, upgrade to Commerce Stripe 8.x-1.4.
- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
Commerce Stripe - Critical - Cross-site request forgery - SA-CONTRIB-2026-263
This module enables you to use the Stripe Connect API to quickly configure your Drupal Commerce store to take payments via multiple Stripe APIs.
When redirecting to Stripe Connect to generate an authorization code, the module does not incorporate a CSRF token into the return URI. This could allow a an attacker to trick an administrator to click a link that bypasses Stripe payment for an order, meaning that the order would be marked as paid without any actual payment.
Solution:Install the latest version:
- Upgrade to Commerce Stripe 2.2.3.
- Commerce Stripe 2.0.x and 2.1.x are no longer supported, so sites on older versions should also update to Commerce Stripe 2.2.3.
- Commerce Stripe 8.x-1.x is not affected.
- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team
Commerce Shipping - Less critical - Access bypass - SA-CONTRIB-2026-262
This module enables you to sell tangible products via Drupal Commerce that are organized into shipments for fulfillment.
The module doesn't sufficiently check access on the form to resend receipts. Under certain configurations, this allows some users to gain access to receipts and customer information for orders they should not be able to access.
Solution:Install the latest version:
- If you use Commerce Shipping 3.0.x, upgrade to Commerce Shipping 3.0.6.
- If you use Commerce Shipping 8.x-2.x, upgrade to Commerce Shipping 8.x-2.16.
- Swan Kalata (akalata) of the Drupal Security Team
- Greg Knaddison (greggles) of the Drupal Security Team
- Juraj Nemec (poker10) of the Drupal Security Team
- Jess (xjm) of the Drupal Security Team

Neue Kommentare
vor 2 Wochen 5 Tagen
vor 2 Wochen 5 Tagen
vor 2 Wochen 5 Tagen
vor 3 Wochen 11 Stunden
vor 3 Wochen 14 Stunden
vor 8 Wochen 5 Tagen
vor 9 Wochen 1 Tag
vor 9 Wochen 3 Tagen
vor 9 Wochen 5 Tagen
vor 9 Wochen 5 Tagen