{"answers":{"affected":"2 open source packages ship an affected version, including @studiocms/s3-storage. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32101 exists.","fix":"Upgrade @studiocms/s3-storage to 0.3.1 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-32101 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32101 exists.\n\nAffected packages and fixed versions:\n- @studiocms/s3-storage (npm): affected all versions; fixed in 0.3.1\n- @studiocms/s3-storage (npm): affected all versions; fixed in 0.3.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32101/ (Markdown: https://insights.sbomify.com/CVE-2026-32101/index.md)","id":"CVE-2026-32101","markdown":"https://insights.sbomify.com/CVE-2026-32101/index.md","name":"CVE-2026-32101","record":{"aliases":["GHSA-mm78-fgq8-6pgr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"StudioCMS S3 storage","requires_auth":"low_privilege","summary":"Low-privilege users can bypass authorization checks to upload, delete, and list all files in the S3 bucket due to a missing await keyword.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"studiocms","vendor":"studiocms"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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\u003cboolean\u003e) 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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check","id":"CVE-2026-32101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"OliveTin Unauthorized Action Output Disclosure via EventStream","id":"CVE-2026-32102"},"packages":[{"ecosystem":"npm","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"@studiocms/s3-storage","purl":null,"source":"GHSA-mm78-fgq8-6pgr"},{"ecosystem":"npm","fixed":["0.3.1"],"introduced":["0"],"last_affected":[],"package":"@studiocms/s3-storage","purl":"pkg:npm/%40studiocms/s3-storage","source":"GHSA-mm78-fgq8-6pgr"}],"prev":{"headline":"swag/platform-security: `/api/_info/config` route exposes information about licenses and active security fixes","id":"CVE-2026-32100"},"products":["s3-storage"],"published":"2026-03-11","related":[{"cvss_score":8.8,"headline":"StudioCMS Affected by Privilege Escalation via Insecure API Token Generation","id":"CVE-2026-30944","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.1,"headline":"StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service","id":"CVE-2026-30945","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.8,"headline":"StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation","id":"CVE-2026-32103","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":6.5,"headline":"StudioCMS has an Authorization Bypass Through User-Controlled Key","id":"CVE-2026-24134","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":5.4,"headline":"StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings","id":"CVE-2026-32104","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":4.7,"headline":"StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts","id":"CVE-2026-32106","kev_date_added":null,"published":"2026-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["@studiocms"]},"summary":"Low-privilege users can bypass authorization checks to upload, delete, and list all files in the S3 bucket due to a missing await keyword.","url":"https://insights.sbomify.com/CVE-2026-32101/"}