Is CVE-2026-96398 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-96398 being exploited in the wild.

How severe is CVE-2026-96398?

Informational severity, published 22 October 2026.

Which products and versions are affected?

Drupal Webform before 6.2.12 or 6.3.0 before 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-96398?

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-96398 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-96398?

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.

CVE-2026-96398: Drupal Webform module access bypass in submission view modes

CVE-2026-96398 · Severity: info · Published 2026-10-22

The Webform module for Drupal allows site builders to create and manage forms and collect user submissions with restricted access controls. A vulnerability in access control permits users who can view a submission to access more permissive view modes and see restricted fields they should not access. The risk is mitigated by the requirement that an attacker must already have legitimate access to view the affected submission.

Technologies: Drupal Webform, Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform. Vendors: Drupal, Packagist:Https://Packages.Drupal.Org/8.

Quick answers

Is CVE-2026-96398 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-96398 being exploited in the wild.
How severe is CVE-2026-96398?: Informational severity, published 22 October 2026.
Which products and versions are affected?: Drupal Webform before 6.2.12 or 6.3.0 before 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-96398?: 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-96398 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-96398?: 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 does not sufficiently restrict access to certain submission view modes, allowing an authenticated user with submission viewing permissions to escalate to a more permissive view mode and access restricted fields. This is an access bypass vulnerability requiring prior submission access. Patches are available in versions 6.2.12 and 6.3.1.

Affected products

Drupal Webform before 6.2.12 or 6.3.0 before 6.3.1

Identifiers

CVE-2026-96398
DRUPAL-CONTRIB-2026-173

Timeline

2026-09-23: disclosed
2026-09-23: patched: Versions 6.2.12 and 6.3.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.