dbcve.org
Artificial IntelligenceDrupal extension · Artificial Intelligence Project

CVE-2026-3573

HIGH · 7.5 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 1.1.11 / 1.2.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect Authorization vulnerability in Drupal AI (Artificial Intelligence) allows Resource Injection.This issue affects AI (Artificial Intelligence): from 0.0.0 before 1.1.11, from 1.2.0 before 1.2.12.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Drupal AI module versions prior to 1.1.11 and 1.2.12 contain an incorrect authorization vulnerability that allows authenticated users to perform resource injection, potentially enabling unauthorized access to AI resources or manipulation of AI operations.

MitigationUpdate the Drupal AI module to version 1.1.11 or 1.2.12 or later to resolve the authorization bypass. Review user role permissions and audit access logs for suspicious AI resource activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Artificial IntelligenceDrupal extension
Affected:< 1.1.11>= 1.2.0, < 1.2.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Drupal AI module is installed
    In the Drupal admin dashboard, navigate to Extend (admin/modules) and search for 'Artificial Intelligence' or 'AI' module. Alternatively, check the codebase for the ai module in /modules/contrib/ai/ or run: drush pm-list --type=module --status=enabled | grep -i ai
    Affected if The AI module appears in the list of installed/enabled modules
  2. Determine installed AI module version
    Check the ai.info.yml file in the module directory, or run: drush pm:info ai. Look for the Version field in the output.
    Affected if The version displayed is less than 1.1.11, or greater than or equal to 1.2.0 but less than 1.2.12
  3. Confirm AI module resource features are accessible
    Navigate to People > Roles (admin/config/people/roles) and check which roles have permissions related to AI operations (such as 'Use AI agents', 'Access AI resources', or similar AI-related permissions). Verify if authenticated users or non-admin roles have been granted these permissions.
    Affected if Authenticated users (authenticated user role) or other non-administrative roles have been assigned AI resource or AI operation permissions
  4. Inspect AI module configuration for resource injection settings
    Navigate to Configuration > AI settings (admin/config/ai) or check the ai.settings.yml configuration file. Look for settings related to resource endpoints, external AI service connections, or resource injection paths that could be manipulated.
    Affected if The module exposes configurable AI resource endpoints or external service connections that authenticated users can modify or access
  5. Review access logs for AI resource activity
    Check Drupal logs (admin/reports/dblog) or external logging for entries related to AI module endpoints. Look for requests to AI resource paths from user accounts that should not have elevated AI access.
    Affected if Logs show AI resource access or manipulation attempts from authenticated users who should not have such access based on your intended role permissions

Your environment is affected if the Drupal AI module is installed and enabled with a version prior to 1.1.11 or between 1.2.0 and 1.2.11 inclusive, and authenticated users have AI resource access permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.11 / 1.2.12 or later
Fixed in 1.1.111.2.12
Interim mitigation

Update the Drupal AI module to version 1.1.11 or 1.2.12 or later to resolve the authorization bypass. Review user role permissions and audit access logs for suspicious AI resource activity.

Recommended fix High confidence

Drupal AI module version 1.1.11 (for 1.x branches) or 1.2.12 (for 1.2.x branch)

  1. Identify the currently installed version of the Drupal AI module by reviewing composer.json or the Drupal admin interface
  2. For sites running AI module versions below 1.1.11: Run 'composer require drupal/ai:1.1.11' to upgrade to the first fixed release
  3. For sites running AI module versions 1.2.0-1.2.11: Run 'composer require drupal/ai:1.2.12' to upgrade to the first fixed release
  4. After upgrading, clear the Drupal cache using 'drush cr' or via the admin interface at /admin/config/development/performance
  5. Verify the upgrade was successful by checking the module version at /admin/modules or via 'drush pm:list | grep ai'
  6. Review the module's functionality to ensure the authorization fix does not break existing workflows
Caveat Review the module's release notes at www.drupal.org/project/ai/releases to confirm no breaking changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Artificial Intelligence Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3573 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data