Peter Brady, Drupal developer and private AI consultant

Drupal security updates, in plain English · Module

AI (Artificial Intelligence)

23,475 sites report using it · on drupal.org · 3 security updates explained here

This module automatically translates pieces of content.

Below is every security update for AI (Artificial Intelligence) that this site has covered, newest first. Each one says who could exploit it, whether it applies to your site, how urgent it is, and what to tell your developer. If your site uses this module and you are not sure which version, that is the first question to ask whoever looks after it.

AI (Artificial Intelligence)

Moderately critical · 23,475 sites report using it · 2 security fixes · Week of 2 September 2026

2 security fixes in one update. AI (Artificial Intelligence) fixed 2 separate security bugs this week: 1 access bypass, 1 cross site scripting. One update covers all of them. The most serious, SA-CONTRIB-2026-120, is explained here and the full list is at the end of the card.

The module does not properly check access rights on related fields or referenced items during translation. A user with an ordinary account could translate items they should not have access to. They could not read or update the affected items in other ways.

  • Who could do thisOnly someone with a login on your site.
  • Does it apply to youAny site using this module.
  • Has it been used in attacksNo sign of it.
  • How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.

Tell your developerUpdate AI (Artificial Intelligence) to 1.3.13 or 1.4.8, whichever branch you are on.

For developers: what the fix changed

This release carries 2 security fixes. The summary below is for SA-CONTRIB-2026-120, the most serious of them.

This fix adds a custom access callback named `checkAccess` in `AiTranslateController.php` to verify entity update and translation access. It also introduces field and referenced entity access checks in `TextExtractor.php` and `ReferenceFieldExtractor.php` to ensure users can only translate content they are permitted to view and update.

Also in this release The release also fixes a cross site scripting vulnerability in the AI Chatbot module by filtering YAML output and updates package versions.

1.3.12 to 1.3.13 5 commits, 10 files.

  • modules/ai_chatbot/src/Controller/DeepChatApi.php +1 −1
  • modules/ai_chatbot/src/Form/ChatForm.php +3 −3
  • modules/ai_ckeditor/package-lock.json +2 −2
  • modules/ai_ckeditor/package.json +1 −1
  • modules/ai_translate/ai_translate.routing.yml +2 −1 fix
  • modules/ai_translate/src/Controller/AiTranslateController.php +61 −1 fix
  • modules/ai_translate/src/Plugin/FieldTextExtractor/ReferenceFieldExtractor.php +2 −2 fix
  • modules/ai_translate/src/TextExtractor.php +4 −0 fix
  • ui/mdxeditor/package-lock.json +2 −2
  • ui/mdxeditor/package.json +1 −1

Full diff, 1.3.12 to 1.3.13 · Full diff, 1.4.7 to 1.4.8

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

All 2 security bugs this update fixes, worst first. Each link is the drupal.org notice for that one.

AI (Artificial Intelligence)

Moderately critical · 23,475 sites report using it · 2 security fixes · Week of 24 June 2026

2 security fixes in one update. AI (Artificial Intelligence) fixed 2 separate security bugs this week: 1 access bypass, 1 information disclosure / cross site scripting. One update covers all of them. The most serious, SA-CONTRIB-2026-055, is explained here and the full list is at the end of the card.

An administrator account could use an artificial intelligence agent to bypass access checks for certain website actions. They could view restricted system settings and modify specific automated workflows. They could not access or alter every piece of information on the website.

  • Who could do thisOnly someone with an administrator login.
  • Does it apply to youA site is affected if an attacker has access to communicate with an affected agent and the site is set up to expose the affected tools to users without special access rights.
  • Has it been used in attacksNo sign of it.
  • How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.

Tell your developerUpdate AI (Artificial Intelligence) to 1.2.17, 1.3.8 or 1.4.3, whichever branch you are on.

For developers: what the fix changed

This release carries 2 security fixes. The summary below is for SA-CONTRIB-2026-055, the most serious of them.

The fix introduces an `access()` method in `ActionPluginBase` to ensure proper access validation before executing core actions exposed as agent tools, mapping specific actions to required permissions and delegating entity actions to entity access checks. It also updates `RagAction` to enforce access control by default and provides an update hook to migrate existing configurations.

Also in this release The release also adds URL filtering hardening, MIME type validation for AI-generated files, and a SECURITY.md file.

1.2.16 to 1.2.17 7 commits, 15 files including 4 tests.

  • .cspell-project-words.txt +6 −0
  • .gitlab-ci.yml +1 −1
  • SECURITY.md +36 −0
  • docs/contribute/releases/tagging_a_release.md +1 −1
  • docs/security.md +9 −0
  • mkdocs.yml +1 −0
  • modules/ai_search/ai_search.install +35 −0 fix
  • modules/ai_search/src/Plugin/AiAssistantAction/RagAction.php +20 −5 fix
  • src/Base/OpenAiBasedProviderClientBase.php +56 −13
  • src/Plugin/AiFunctionCall/ActionPluginBase.php +108 −4 fix
  • src/Service/HostnameFilter.php +93 −4

Full diff, 1.2.16 to 1.2.17 · Full diff, 1.3.7 to 1.3.8 · Full diff, 1.4.2 to 1.4.3

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

All 2 security bugs this update fixes, worst first. Each link is the drupal.org notice for that one.

AI (Artificial Intelligence)

Moderately critical · 23,475 sites report using it · SA-CONTRIB-2026-028 · on drupal.org · Week of 11 March 2026

A visitor without an account could see secret messages sent between the website and the artificial intelligence service. They could read this private information when the website shows a preview of generated text. They could not change any settings or alter the messages.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youAny site using this module.
  • Has it been used in attacksNo sign of it.
  • How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.

Tell your developerUpdate AI (Artificial Intelligence) to 1.1.11 or 1.2.12, whichever branch you are on.

For developers: what the fix changed

The fix introduces a `HostnameFilter` service (`src/Service/HostnameFilter.php`) to sanitise AI-generated HTML and Markdown by removing or rewriting links and images pointing to untrusted external domains. This filter is applied to both standard and streamed chat outputs in `src/Plugin/ProviderProxy.php` and `src/OperationType/Chat/StreamedChatMessageIterator.php`, preventing data exfiltration via prompt injection.

Also in this release Added configuration options and UI for the hostname filter in the settings form, along with related schema updates and tests.

1.1.10 to 1.1.11 1 commit, 20 files including 2 tests.

  • .cspell-project-words.txt +11 −0
  • ai.install +14 −0
  • ai.module +15 −0
  • ai.services.yml +4 −1
  • config/install/ai.settings.yml +2 −0
  • config/schema/ai.schema.yml +8 −0
  • docs/developers/hostname_filter.md +122 −0
  • modules/ai_automators/src/PluginBaseClasses/Link.php +44 −26 fix
  • modules/ai_automators/src/PluginBaseClasses/RuleBase.php +7 −0 fix
  • src/AiProviderPluginManager.php +11 −1
  • src/Dto/HostnameFilterDto.php +75 −0
  • src/Form/AiSettingsForm.php +55 −0

Full diff, 1.1.10 to 1.1.11 · Full diff, 1.2.11 to 1.2.12

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

Not sure what your site is running?

Send me your Drupal site's address.

I'll tell you what I can see from outside, what the Drupal 10 end of life on 9 December means for it, and what it would cost to have me keep it patched. There's no charge for that and no obligation. peter@peterbrady.co.uk

Get in touch

Tell me who you are, what your organisation does, and what you need. That might be a Drupal site that needs looking after, an upgrade to get done before December, or an agency that needs Drupal cover.

If I can help, I'll say so and suggest a call. If I can't, I'll tell you straight away rather than waste your time.

peter@peterbrady.co.uk

For context: I work mainly with UK charities, membership bodies and research organisations, and with the agencies that look after their websites. Not recruiters.

Or start smaller and connect with me on LinkedIn. That's where I post what I find digging around in charity and grants data, and where the free tools turn up first.

Peter Brady, Drupal developer and private AI consultant

PNB Technologies Limited
55 Yew Tree Road, Ormskirk
Lancashire, L39 1NT, United Kingdom

Company Reg: 07166600
VAT Reg: GB986726850

© 2026 Peter Brady. All rights reserved.

Connect on LinkedIn

Links

Reference