Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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.
Recommended action: Upgrade to 4.0.0-canary.34 (pre-release) or 3.90.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact 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 Patches This vulnerability has been patched in v3.78.0. Filename validation has been hardened for client uploads. Consumers should upgrade to v3.78.0 or later. Workarounds Consumers can upgrade: - Limit access to client-upload signed-URL endpoints to trusted users only.
Recommended action: Upgrade to 3.78.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.