Authentication Bypass in Drupal Clean RESTful (CVE-2026-15087)
Summary
Authentication bypass in Drupal Clean RESTful (CVE-2026-15087). Confidential information can be exposed externally.
Original description
The description as published by the source.
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-15087 was discovered in Drupal Clean RESTful.
In plain terms, it is an authentication weakness that allows impersonation.
Severity is Medium (CVSS 5.9/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Drupal Clean RESTful CVE-2026-15087".
CVE-2026-15087 (Drupal Clean RESTful). Severity: Medium / CVSSv3 5.9. Category: CWE-287.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-15087) in Drupal Clean RESTful. In plain words, it is an authentication weakness that allows impersonation.
Target versions of Drupal Clean RESTful (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 5.9/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-287)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
References
- web nvd.nist.gov
- web drupal.org
- web github.com