drupal/s3fs_cors · S3fs cors: This module enables you to upload files from the browser directly to Amazon S3 and register them as Drupal
Affects drupal/s3fs_corsSource GCVE Database
Not known to be exploited : upgrade to 1.3.0 soon.
Data as of 4 Nov 2026, 21:07 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.3.0
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade drupal/s3fs_cors to 1.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/s3fs_cors | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the s3fs_cors module to version 1.3.0 or later, where the access control issue has been fixed. Applying this official fix fully mitigates the vulnerability.
Description
The Drupal S3fs CORS module allows direct browser uploads to Amazon S3 and registers them as Drupal files, bypassing PHP file size and timeout limits. A vulnerability exists due to insufficient access checks on file uploads, enabling certain users to delete files they should not have permission to delete. This issue affects versions prior to 1.3.0 and has been fixed in version 1.3.0.