Quick answers
- Is CVE-2026-96365 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96365 being exploited in the wild.
- How severe is CVE-2026-96365?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Drupal Webform <6.2.12, >=6.3.0 <6.3.1; Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform ECOSYSTEM:introduced=0,fixed=6.2.12|ECOSYSTEM:introduced=6.3.0,fixed=6.3.1.
- Is there a fix for CVE-2026-96365?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform: upgrade to 6.2.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96365 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96365?
- Check whether you run Drupal Webform or Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform: upgrade to 6.2.12 or later
Technical details
The Webform module fails to properly validate an optional token query parameter before processing requests, allowing an unauthenticated attacker to trigger resource exhaustion via a specially crafted request. The vulnerability exists in configurations where Webforms are rendered for anonymous visitors. A patch is available in versions 6.2.12, 6.3.1, and later.
Affected products
- Drupal Webform <6.2.12, >=6.3.0 <6.3.1
Identifiers
- CVE-2026-96365
- DRUPAL-CONTRIB-2026-170
Timeline
- 2026-09-23: disclosed