Drupal disclosed CVE-2026-118539, a highly critical missing-authorization flaw in Drupal Commerce Core that it says is actively exploited in the wild. The advisory states the module does not sufficiently protect certain routes and entity fields, leading to an access bypass that may financially impact the vendor, though Drupal gave no detail on the attacks. It affects Commerce Core versions up to 2.41 and from 3.0.0 through 3.3.13, with fixes in Commerce Core 3.3.13 for the 3.x line and 8.x-2.41 for earlier versions. Store operators should update immediately and review orders and permissions for signs of abuse.
Drupal patched CVE-2026-108097, a flaw in the Field UI module it rates 19 out of 25 on its own critical scale. Field UI built admin tables that ran each row's region callback through call_user_func_array without checking the callable, a path present since Drupal 8.9.0 in 2020, and the fix stops calling the callback. Several exploit paths run through contributed modules, and at least one needs no login, raising an unauthenticated remote code execution risk. Fixes are in 11.4.10, 11.3.19, and 10.6.19, with no fix for end-of-life branches. No exploit was public as of mid-October, but the team warned exploits could appear within hours.
CISA has given US federal civilian agencies a midnight Wednesday May 27 deadline to patch CVE-2026-9082, the highly critical Drupal SQL injection added to its Known Exploited Vulnerabilities catalog on Friday. Imperva says it has now observed 15,000+ attack attempts targeting nearly 6,000 individual Drupal sites across 65 countries since disclosure, with gaming and financial services taking almost half. Shadowserver tracks ~670 unpatched Drupal instances still exposed online (272 in North America, 273 in Europe). CISA's directive is mandatory only for FCEB agencies under BOD 22-01, but the agency strongly urges all organizations to patch immediately.
Drupal has issued an update to its highly critical PSA-2026-05-18 advisory confirming that exploit attempts for CVE-2026-9082 are now being detected in the wild. The bug is an SQL injection in Drupal's database abstraction API that lets unauthenticated requests trigger arbitrary SQL on sites running PostgreSQL, with possible escalation to RCE, privilege escalation, and information disclosure. Drupal rates it 23 out of 25 internally though NIST's CVSS v3 score is a mismatched 6.5. CISA added it to KEV on May 22. Affected versions cover Drupal 8.9.x and all 10.x and 11.x branches up to 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, and 11.3.10.
Drupal has shipped the highly critical core security release teased by PSA-2026-05-18. The flaw lets attackers achieve remote code execution on Drupal sites running PostgreSQL backends. Fixed versions are 11.3.10, 11.2.12, 11.1.10, 10.6.9, 10.5.10, and 10.4.10. The releases for supported branches also pull in upstream Symfony and Twig security fixes, making the upgrade essential even on MySQL deployments. Best-effort manual patches are available for end-of-life Drupal 9.5 and 8.9. Drupal 7 is not affected. The Drupal Security Team had warned that working exploits could follow within hours of disclosure, so administrators should patch now.
Drupal is releasing an emergency core security update on May 20 between 17:00 and 21:00 UTC. Pre-disclosure advisory PSA-2026-05-18 rates the issue 'highly critical' (20 of 25 on Drupal's scoring) and notes access complexity 'None' and authentication 'None' - meaning the underlying flaw is unauthenticated and easy to trigger. Patches will land for the supported 11.3.x, 11.2.x, 10.6.x, and 10.5.x branches, plus emergency patches for EOL 11.1.x and 10.4.x. Drupal 7 is not affected. Drupal 8 and 9 will only get best-effort manual patch files. The Drupal Security Team warns working exploits may follow within hours of disclosure.