Drupal AI up to 1.4.11/1.5.2 sensitive information

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.3$0-$5k1.85

Summaryinfo

A vulnerability has been found in Drupal AI up to 1.4.11/1.5.2 and classified as problematic. This vulnerability affects unknown code. This manipulation causes sensitive information. This vulnerability appears as CVE-2026-118551. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Drupal AI up to 1.4.11/1.5.2. It has been declared as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a sensitive information vulnerability. The CWE definition for the vulnerability is CWE-922. The product stores sensitive information without properly limiting read or write access by unauthorized actors. As an impact it is known to affect confidentiality. The summary by CVE is:

Insecure Storage of Sensitive Information vulnerability in Drupal AI (Artificial Intelligence) allows Retrieve Embedded Sensitive Data. This issue affects AI (Artificial Intelligence) versions: from 0.0.0 to 1.4.11, from 1.5.0 to 1.5.2.

The advisory is shared at drupal.org. This vulnerability is known as CVE-2026-118551 since 10/28/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Sensitive information
CWE: CWE-922 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

10/28/2026 CVE reserved
10/30/2026 +2 days Advisory disclosed
10/30/2026 +0 days VulDB entry created
10/30/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: drupal.org

Advisory: drupal.org
Status: Confirmed

CNA: drupal
CVE: CVE-2026-118551 (🔒)

GCVE (CVE): GCVE-0-2026-118551
GCVE (VulDB): GCVE-100-428893

Entryinfo

Created: 10/30/2026 04:45
Changes: 10/30/2026 04:45 (52)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!