drupal/s3fs_cors · S3fs cors: The S3 File System CORS Upload module lets users upload files straight from the browser to Amazon S3 (or an
Affects drupal/s3fs_corsSource GCVE Database
Not known to be exploited : upgrade to 1.4.0 soon.
Data as of 11 Nov 2026, 20:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.4.0
Exploitation evidence
Disclosed: evidence found.
CVE published 11 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 11 Nov 2026.
What to do
Upgrade drupal/s3fs_cors to 1.4.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 S3 File System CORS Upload module to version 1.4.0 or later, where this vulnerability is fixed. Since the vulnerability requires access to a form using the upload widget, restricting access to such forms also mitigates the risk.
Description
The S3 File System CORS Upload module for Drupal allows users to upload files directly from the browser to Amazon S3 or compatible services via a file widget. A vulnerability exists where the module does not sufficiently restrict upload permissions, enabling users with upload access to overwrite existing files in the bucket, including those they normally could not replace. Exploitation requires access to a form using this upload widget. The issue is fixed in version 1.4.0.