PatchSiren cyber security CVE debrief
CVE-2026-96356 Drupal CVE debrief
CVE-2026-96356 is an Incorrect Authorization vulnerability in Drupal Webform, allowing Forceful Browsing. Affected versions include Webform from 0.0.0 to 6.2.12 and from 6.3.0 to 6.3.1. The vulnerability could potentially allow attackers to bypass access controls. Defenders should verify exposure, especially for Webform versions 0.0.0 to 6.2.12 and 6.3.0 to 6.3.1, and consider updates or compensating controls. The vulnerability's impact and exploitation details are limited, requiring verification from official sources.
- Vendor
- Drupal
- Product
- Webform
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-22
- Original CVE updated
- 2026-10-22
- Advisory published
- 2026-10-22
- Advisory updated
- 2026-10-22
Who should care
Drupal Webform users, especially those with versions 0.0.0 to 6.2.12 or 6.3.0 to 6.3.1 installed, should assess their exposure and consider updating or applying compensating controls to mitigate potential risks.
Why it matters
CVE-2026-96356 is an Incorrect Authorization vulnerability in Drupal Webform that allows Forceful Browsing. Defenders should verify exposure, especially for Webform versions 0.0.0 to 6.2.12 and 6.3.0 to 6.3.1, and consider updates or compensating controls. The vulnerability's impact and exploitation details are limited, requiring verification from official sources.
- Verification of Webform version and exposure is necessary to prevent potential unauthorized access.
- Defenders should assess the need for updates or compensating controls to mitigate the risk of Forceful Browsing.
- Understanding the authorization mechanisms in place for Webform can help in identifying potential vulnerabilities.
- Remediation priority should be set based on the sensitivity of the Webform data and the potential impact of unauthorized access.
Technical summary
The vulnerability in Drupal Webform allows for Forceful Browsing due to Incorrect Authorization. This issue affects Webform versions from 0.0.0 to 6.2.12 and from 6.3.0 to 6.3.1. The vulnerability could potentially allow attackers to bypass access controls, although specific exploitation details are not provided.
Defensive priority
Defenders should prioritize verifying exposure in their Webform installations, especially if versions 0.0.0 to 6.2.12 or 6.3.0 to 6.3.1 are in use, and assess the need for updates or compensating controls.
Recommended defensive actions
- Verify Webform version and compare to affected ranges (0.0.0 to 6.2.12, 6.3.0 to 6.3.1).
- Update to a non-affected version if possible.
- Implement compensating controls to restrict access to sensitive Webform functionality.
- Monitor Webform logs for suspicious activity indicative of attempted exploitation.
Evidence notes
The CVE record and source item provide details on the vulnerability and affected versions. However, specific exploitation instances or detailed impact assessments are not provided, limiting the ability to fully understand the vulnerability's effects.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-96356 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-96356
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-96356 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-96356
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Webform - Moderately critical - Access bypass - SA-CONTRIB-2026-174
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/96xxx/CVE-2026-96356.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://www.drupal.org/sa-contrib-2026-174
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.