GHSA-p223-2wr2-j562: Path Traversal

Published Oct 7, 2026
·
Updated

Impact Under certain conditions, an authenticated user with permission to modify uploads could cause unintended files to be removed during file cleanup. This may result in data loss or service disruption.

You are affected if: - You use Payload upload collections with local file storage. - Untrusted authenticated users can update or delete uploads.

Deployments that restrict upload management to trusted users are less exposed.

Patches Payload now validates uploaded filenames and ensures file cleanup remains within the configured upload directory.

Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

Workarounds Restrict upload update and deletion operations to trusted users and validate submitted filenames. These measures are temporary mitigations. Upgrading to a patched version is recommended.

Affected Software

2 affected componentsFixes available
npm/payload>=4.0.0-canary.0<4.0.0-canary.34
4.0.0-canary.34
npm/payload<3.90.0
3.90.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  2. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 3.90.0
  3. Upgrade

    Upgrade Payload packages to a version that resolves this vulnerability.

    Fixed in 3.90.0
  4. Upgrade

    Upgrade Payload packages to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  5. Compensating control

    Restrict upload update and deletion operations to trusted users.

  6. Compensating control

    Validate submitted upload filenames and ensure file cleanup remains within the configured upload directory.

Event History

Oct 7, 2026
Advisory Published
via GitHub·08:29 PM
Data Sourced
via GitHub·08:29 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are most exposed?

Deployments using Payload upload collections with local file storage are affected when untrusted authenticated users can update or delete uploads. Restricting upload management to trusted users reduces exposure.

2

What access does an attacker need?

An attacker must be authenticated and have permission to modify uploads. Exploitation is associated with upload update or deletion operations under certain conditions.

3

What can be done before upgrading?

Restrict upload update and deletion operations to trusted users and validate submitted filenames. These are temporary mitigations; upgrading is recommended.

4

Which versions contain the fix?

Upgrade Payload packages to version 3.90.0 or later, or to 4.0.0-canary.34 or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203