Skip to content

feat: update advisories #272

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DrupalSecurityBot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: update advisories #272

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions advisories/ai_provider_amazeeio/DRUPAL-CONTRIB-2026-134.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
{
"schema_version": "1.7.0",
"id": "DRUPAL-CONTRIB-2026-134",
"modified": "2026-09-09T17:14:57.000Z",
"modified": "2026-09-11T12:42:14.000Z",
"published": "2026-09-09T17:14:00.000Z",
"aliases": [
"CVE-2026-87936"
],
"details": "This module integrates amazee.ai's AI services into Drupal, including a Postgres/pgvector vector database backend for use with Search API AI Search.\n\nThe module doesn't sufficiently sanitize filter values before using them to build SQL queries in its Postgres/pgvector backend, allowing SQL injection.\n\nThis vulnerability is mitigated by the fact that a site must be using the module's Postgres/pgvector vector database backend for a Search API AI Search index, and must expose one of that index's non-string fields as a filter (for example, through a View) that is reachable by the attacker.",
"details": "**Update 2026-09-11:** Increased risk score to reflect publicly documented methods for developing exploits.\n\nThis module integrates amazee.ai's AI services into Drupal, including a Postgres/pgvector vector database backend for use with Search API AI Search.\n\nThe module doesn't sufficiently sanitize filter values before using them to build SQL queries in its Postgres/pgvector backend, allowing SQL injection.\n\nThis vulnerability is mitigated by the fact that a site must be using the module's Postgres/pgvector vector database backend for a Search API AI Search index, and must expose one of that index's non-string fields as a filter (for example, through a View) that is reachable by the attacker.",
"affected": [
{
"package": {
Expand Down