Advisories for Npm/@Payloadcms/Storage-S3 package

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.

The client-upload signed-URL endpoints for S3, GCS, Azure, and R2 did not properly sanitize filenames. An attacker could craft filenames to escape the intended storage location. Consumers are affected if ALL of these are true: Payload version < v3.78.0 Using client-upload signed-URL endpoints for any supported storage adapter