CVE-2026-118582: Drupal CAPTCHA · Authentication Bypass Using an Alternate Path or Channel
Affects Drupal CAPTCHASource CVE Database V5
Not known to be exploited : upgrade to 2.0.11 or 1.18.0 soon.
Data as of 30 Oct 2026, 03:45 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.0.11, 1.18.0
Exploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Drupal CAPTCHA to 2.0.11 or 1.18.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DrupalCAPTCHA | Affected
| Fixed in
|
| DrupalCAPTCHA | Affected
| Fixed in
|
AI-suggested
Apply the official fixes by upgrading the Drupal CAPTCHA module to version 1.18.0 or later in the 1.x series, or to version 2.0.11 or later in the 2.x series. Since fixed versions are publicly known, patching is the recommended and effective mitigation.
Description
CVE-2026-118582 is an authentication bypass vulnerability in the Drupal CAPTCHA module. It allows attackers to bypass functionality by using an alternate path or channel. The issue affects CAPTCHA versions from 0.0.0 up to but not including 1.18.0, and from 2.0.0 up to but not including 2.0.11. Fixed versions are 1.18.0 and 2.0.11.