Is CVE-2026-96357 exploited in the wild?

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

How severe is CVE-2026-96357?

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-96357?

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

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

Am I affected by CVE-2026-96357?

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-96357: Drupal Webform module cross-site scripting in file download handling

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

The Webform module for Drupal allows site administrators to build forms and collect user submissions, including file uploads. A misconfiguration in how uploaded files are served could cause certain file types to be displayed inline in a browser rather than downloaded, enabling attackers to inject malicious scripts. An attacker would need form creator permissions to enable vulnerable file types and a victim to open a malicious uploaded file.

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

Quick answers

Is CVE-2026-96357 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-96357 being exploited in the wild.
How severe is CVE-2026-96357?: 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-96357?: 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-96357 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-96357?: 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 a stored cross-site scripting (XSS) flaw in the Webform module's file serving mechanism. The module fails to force Content-Disposition: attachment headers for certain file types, allowing inline rendering instead of download. Under specific site configurations, an uploaded file with dangerous content (e.g., HTML or SVG with embedded scripts) could execute in a user's browser when accessed, though exploitation requires both form creator permissions and user interaction.

Affected products

Drupal Webform before 6.2.12, or 6.3.0 before 6.3.1

Identifiers

CVE-2026-96357
DRUPAL-CONTRIB-2026-172

Timeline

2026-09-23: disclosed

References

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