Quick answers
- Is CVE-2026-96362 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96362 being exploited in the wild.
- How severe is CVE-2026-96362?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Drupal Webform before 6.2.12, 6.3.0 to 6.3.0; 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-96362?
- 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-96362 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-96362?
- 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 sanitize response values from Remote Post handlers before rendering them through handler response tokens. The vulnerability requires an attacker to control or influence the response from a configured remote API endpoint, and the site must use those response tokens in rendered output. XSS injection in rendered HTML is the result; the vulnerability is fixed in versions 6.2.12 and 6.3.1.
Affected products
- Drupal Webform before 6.2.12, 6.3.0 to 6.3.0
Identifiers
- CVE-2026-96362
- DRUPAL-CONTRIB-2026-160
Timeline
- 2026-09-23: disclosed
- 2026-09-23: patched: Patched in versions 6.2.12 and 6.3.1