Drupal security updates, in plain English · Module

amazee.ai Private AI Provider

8,283 sites report using it · on drupal.org · 1 security update explained here

This module connects the website to artificial intelligence services and provides a database for intelligent search features.

Below is every security update for amazee.ai Private AI Provider 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.

amazee.ai Private AI Provider

Critical · 8,283 sites report using it · SA-CONTRIB-2026-134 · on drupal.org · Week of 9 September 2026

The module does not properly clean up search filters before using them to query the database. Anyone visiting the site could run malicious database commands to read any private information and change some data.

  • Who could do thisAnyone visiting the site. No login needed.
  • Does it apply to youA site is affected if it uses the module for intelligent search and exposes a specific type of search filter to visitors.
  • Has it been used in attacksA working example has been published, so assume someone will try.
  • How urgentDrupal rates this critical. Cyber Essentials expects a fix within 14 days. Do it this week.

Tell your developerUpdate amazee.ai Private AI Provider to 1.3.7 or 1.4.3, whichever branch you are on.

For developers: what the fix changed

The fix updates `PostgresProvider.php` to quote all Search API filter values using `prepareStringArrayForSql` regardless of their field type, preventing SQL injection. It also removes the insecure `prepareArrayForSql` method from `PostgresPgvectorClient.php`.

Also in this release The release also fixes an issue where key provisioning requests would time out and retry by increasing the timeout and disabling retries.

1.3.6 to 1.3.7 2 commits, 5 files including 2 tests.

  • src/AmazeeIoApi/AmazeeClient.php +8 −3
  • src/Vdb/Postgres/Plugin/VdbProvider/PostgresProvider.php +3 −8 fix
  • src/Vdb/Postgres/PostgresPgvectorClient.php +0 −14 fix

Full diff, 1.3.6 to 1.3.7 · 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.

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.