npm package reportIs @payloadcms/storage-s3 safe ? 1 known vulnerability, worst severity HIGH.
// reach 0 direct dependencies
none carry a known advisory
0 packages depend on it
an advisory here reaches each of them
// ai model usage Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
epss chance of exploitation in 30 days
xyz score CyberXYZ composite out of 10
fig. 01 — GHSA-7vg8-29qx-jgj8, the advisory selected below
// 1 advisories GHSA-7vg8-29qx-jgj8 An authenticated user could overwrite an existing S3 object belonging to another upload collection, bypassing that collection’s access controls and prior file validation. HIGH // impact An authenticated user could overwrite an existing S3 object belonging to another upload collection, bypassing that collection’s access controls and prior file validation.
You are affected if ALL of these are true:
Client uploads are enabled for multiple collections that share an S3 bucket. useCompositePrefixes is not configured or is set to false. // patches Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
// workarounds Disable client uploads until you can upgrade.
// cvss v4.0 vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
Attack vector Network
Attack complexity Low
Attack requirements None
Privileges required Low
User interaction None
Confidentiality (vulnerable system) None
Integrity (vulnerable system) High
Availability (vulnerable system) Low
Confidentiality (subsequent systems) None
Integrity (subsequent systems) None
Availability (subsequent systems) None Checked 2026-10-07 at 23:55 UTC. The most recent advisory here was published 2026-10-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.
Think a verdict here is wrong? Tell us — we respond within 2 business days. Report an issue with this page