# CVE-2026-32101: StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check

> Low-privilege users can bypass authorization checks to upload, delete, and list all files in the S3 bucket due to a missing await keyword.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-mm78-fgq8-6pgr

## What is CVE-2026-32101?

CVE-2026-32101 is a high-severity missing authorization vulnerability in @studiocms s3-storage, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.3.1, the S3 storage manager's isAuthorized() function is declared async (returns Promise<boolean>) but is called without await in both the POST and PUT handlers. Since a Promise object is always truthy in JavaScript, !isAuthorized(type) always evaluates to false, completely bypassing the authorization check. Any authenticated user with the lowest visitor role can upload, delete, rename, and list all files in the S3 bucket. This vulnerability is fixed in 0.3.1.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-32101?

2 open source packages ship an affected version, including @studiocms/s3-storage. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@studiocms/s3-storage` | npm | All versions | 0.3.1 |
| `@studiocms/s3-storage` | npm | All versions | 0.3.1 |

Products: Studiocms Studiocms.

## How do I fix CVE-2026-32101?

Upgrade @studiocms/s3-storage to 0.3.1 or later.

## Is CVE-2026-32101 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32101 exists.

## Other vulnerabilities in @studiocms s3-storage

- [CVE-2026-30944](https://insights.sbomify.com/CVE-2026-30944/): StudioCMS Affected by Privilege Escalation via Insecure API Token Generation (high 8.8)
- [CVE-2026-30945](https://insights.sbomify.com/CVE-2026-30945/): StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service (high 7.1)
- [CVE-2026-32103](https://insights.sbomify.com/CVE-2026-32103/): StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation (medium 6.8)
- [CVE-2026-24134](https://insights.sbomify.com/CVE-2026-24134/): StudioCMS has an Authorization Bypass Through User-Controlled Key (medium 6.5)
- [CVE-2026-32104](https://insights.sbomify.com/CVE-2026-32104/): StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32101 and fix it if it is affected.

What it is: CVE-2026-32101 is a high-severity missing authorization vulnerability in @studiocms s3-storage, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32101 exists.

Affected packages and fixed versions:
- @studiocms/s3-storage (npm): affected all versions; fixed in 0.3.1
- @studiocms/s3-storage (npm): affected all versions; fixed in 0.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32101/ (Markdown: https://insights.sbomify.com/CVE-2026-32101/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32101
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32101
- OSV: https://osv.dev/vulnerability/CVE-2026-32101

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32101/
Summaries are generated and may contain mistakes; the official description above is the record.