Quick answers
- Is CVE-2026-96361 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96361 being exploited in the wild.
- How severe is CVE-2026-96361?
- 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-96361?
- 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-96361 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96361?
- 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 exists in insufficient sanitization of text counter configuration options before passing them to the bundled jQuery Text Counter library, allowing unsanitized markup to reach the client-side JavaScript. The attack requires elevated privileges (ability to create or edit Webform elements) or placement of specially crafted counter markup on a page where the Webform counter JavaScript is active. A successful exploit results in cross-site scripting execution within the context of the affected page.
Affected products
- Drupal Webform <6.2.12 or >=6.3.0 <6.3.1
Identifiers
- CVE-2026-96361
- DRUPAL-CONTRIB-2026-155
Timeline
- 2026-09-23: disclosed
- 2026-09-23: patched: versions 6.2.12 and 6.3.1 available