Skip to main content
Blue Moose logo Blue Moose Field notes
← All articles
drupal

Two Drupal upload modules, two authorization gaps

Rows of illuminated server racks in a data center

Two Drupal contrib advisories landed on the same day, 11 November, and they rhyme: both are about upload widgets that hand out more power than the form they sit on should allow. Neither is a catastrophe, both are rated moderately critical, but if you've bolted "big file" or "direct to S3" uploads onto a Drupal site, they're worth five minutes of your time.

File Resumable Upload: partial data for strangers

SA-CONTRIB-2026-338 (CVE-2026-126747) covers File Resumable Upload, the module that adds large, multiple and resumable uploads to File and Image field widgets. Versions before 2.0.6 don't sufficiently check access to the resumable upload forms. An unauthenticated user can start uploads against forms they aren't permitted to use and leave partial upload data on the server.

The advisory scores it 13/25 and rates the impact as integrity only, with no confidentiality loss. Two mitigating factors are listed: partial data only attaches to content through the normal entity form, which enforces its own access checks, and the stored data can't be executed by the web server. The fix is simply to upgrade to 2.0.6.

My reading: the realistic worst case is disk filling with junk from anonymous visitors, not code execution. That's my inference, not something the advisory states, so check your own temp storage if you run this module.

S3 File System CORS Upload: overwrite what you shouldn't

SA-CONTRIB-2026-337 (CVE-2026-126746) is the more interesting one. The S3 File System CORS Upload module lets the browser upload straight to Amazon S3 or an S3-compatible service through a file widget on entity forms. Versions before 1.4.0 don't adequately restrict the upload permission the browser is granted. A user who can use the widget can overwrite files already in the bucket, including ones they couldn't otherwise replace. The fixed release is 8.x-1.4, and the score is 11/25.

The attacker does need access to a form that uses the widget, so this is an authenticated-user problem on most sites. But on a site where contributors can upload and the bucket also holds site assets, "overwrite any object" is a real integrity hole.

The pattern behind both

Direct-to-storage and chunked uploads move the access decision out of Drupal's normal request path. Once the browser talks to S3 with a presigned grant, or posts chunks to a custom endpoint, Drupal's entity access system only gets a vote if the module deliberately asks it. Both advisories are the module forgetting to ask, or asking too loosely.

What I'm doing about it:

  • Running composer show drupal/file_resup drupal/s3fs_cors on my sites to see whether either is installed at all.
  • Updating to 2.0.6 and 8.x-1.4 where they are.
  • Checking the bucket policy: if uploads and site assets share a bucket, I'd rather split them than trust a widget's grant.

Cheap upload features rarely come with a threat model attached. Treat any module that bypasses the normal file upload path as security-sensitive code, and put its updates on the fast lane.

BM
Blue Moose
The moose behind Blue Moose. Full-stack PHP developer — Drupal by day, Symfony by night, tests always.