Critical SQL Injection Vulnerability (CVE-2026-9082) in Drupal Actively Exploited in the Wild

Views: 387 views

280/69 Monday, May 25, 2026

On May 20, 2026, Drupal released security patches to address a critical SQL Injection vulnerability tracked as CVE-2026-9082. However, less than 48 hours after the security update was published, researchers observed widespread exploitation attempts targeting vulnerable Drupal websites using PostgreSQL databases. The vulnerability allows unauthenticated attackers to gain access to and potentially take control of affected systems without requiring valid credentials. The incident is particularly significant because many enterprise organizations, educational institutions, and media websites rely on Drupal and may be directly exposed to this threat.

The vulnerability stems from improper filtering within an API responsible for handling database queries, allowing attackers to inject specially crafted SQL commands into PostgreSQL database operations. The impact ranges from sensitive data exposure and privilege escalation to potential remote code execution. Preliminary reports from cybersecurity researchers indicate that more than 15,000 attack attempts have already been detected across 65 countries, with over half targeting the gaming and financial sectors. Statistical data also revealed that the top five targeted countries are the United States (61.8%), Singapore (6.6%), Australia (6.3%), France (4.9%), and Spain (4.3%). Researchers noted that current attacker activity is primarily focused on identifying vulnerable systems before escalating toward large-scale data theft operations.

To reduce risk and prevent compromise, administrators running Drupal with PostgreSQL databases should immediately apply the latest security patches. Systems using other database platforms such as MySQL or MariaDB are reportedly not affected by this vulnerability; however, administrators are strongly advised to verify the exact database technology in use. Organizations should also enhance monitoring of system and database logs for suspicious SQL queries, unusual authentication failures, or other anomalous activity. If indicators of compromise are detected, incident investigation procedures should begin immediately, as the window between reconnaissance and full-scale exploitation appears to be extremely short.

Source https://securityaffairs.com/192557/security/cve-2026-9082-drupals-highly-critical-sql-injection-flaw-is-already-under-active-attack.html