Quick answers
- Is CVE-2026-96372 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96372 being exploited in the wild.
- How severe is CVE-2026-96372?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Drupal Webform <6.2.12 or >=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-96372?
- 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-96372 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96372?
- 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 vulnerability is an authorization bypass affecting the Remote HTTP Operations feature in the Webform module. A user with permission to edit a webform can configure remote HTTP operations without the new "Administer webform remote post URLs" permission, allowing them to send form submissions to attacker-controlled endpoints. The vulnerability requires the attacker to already have the role permission to edit webforms, which mitigates exposure but remains a privilege escalation concern within authenticated contexts.
Affected products
- Drupal Webform <6.2.12 or >=6.3.0, <6.3.1
Identifiers
- CVE-2026-96372
- DRUPAL-CONTRIB-2026-167
Timeline
- 2026-09-23: disclosed