Quick answers
- Is CVE-2026-96369 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96369 being exploited in the wild.
- How severe is CVE-2026-96369?
- 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-96369?
- 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-96369 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96369?
- 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 improper cache variation flaw in the Webform module's JSON:API integration. When a webform is configured to allow authenticated users to view their own submissions, the collection endpoint may return cached responses that were generated for a different user, bypassing access controls. The attack requires JSON:API to be enabled, the webform to expose submissions through JSON:API, and the attacker to possess an authenticated account with view-own-submissions permission.
Affected products
- Drupal Webform <6.2.12, >=6.3.0 <6.3.1
Identifiers
- CVE-2026-96369
- DRUPAL-CONTRIB-2026-165
Timeline
- 2026-09-23: disclosed