CVE-2026-27567: Payload has Server-Side Request Forgery (SSRF) in External File URL Uploads

Published Feb 24, 2026
·
Updated

Impact

A Server-Side Request Forgery (SSRF) vulnerability exists in Payload's external file upload functionality. When processing external URLs for file uploads, insufficient validation of HTTP redirects could allow an authenticated attacker to access internal network resources.

Users are affected if ALL of these are true:

- Payload version < v3.75.0 - At least one collection with upload enabled - A user has create access to that upload-enabled collection

An authenticated user with upload collection write permissions could potentially access internal services. Response content from internal services could be retrieved through the application.

Patches

This vulnerability has been patched in v3.75.0. Users should upgrade to v3.75.0 or later.

Workarounds

If users cannot upgrade immediately, they can mitigate this vulnerability by disabling external file uploads via the disableExternalFile upload collection option, or by restricting create access on upload-enabled collections to trusted users only.

Other sources

Payload is a free and open source headless content management system. Prior to 3.75.0, a Server-Side Request Forgery (SSRF) vulnerability exists in Payload's external file upload functionality. When processing external URLs for file uploads, insufficient validation of HTTP redirects could allow an authenticated attacker to access internal network resources. The Payload environment must have at least one collection with upload enabled and a user who has create access to that upload-enabled collection in order to be vulnerable. An authenticated user with upload collection write permissions could potentially access internal services. Response content from internal services could be retrieved through the application. This vulnerability has been patched in v3.75.0. As a workaround, one may mitigate this vulnerability by disabling external file uploads via the disableExternalFile upload collection option, or by restricting create access on upload-enabled collections to trusted users only.

— MITRE

Affected Software

3 affected componentsFixes available
npm/payload<3.75.0
npm/payload<3.75.0
3.75.0
PayloadCMS Payload Node.js<3.75.0

Event History

Feb 24, 2026
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:21 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·08:10 PM
Data Sourced
via GitHub·08:10 PM
DescriptionSeverityWeaknessAffected Software
Jan 4, 58137
Event
via FIRST·09:42 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-27567?

CVE-2026-27567 is classified as a critical severity vulnerability due to its potential for exploitation via Server-Side Request Forgery.

2

How do I fix CVE-2026-27567?

To mitigate CVE-2026-27567, upgrade Payload to version 3.75.0 or later, which addresses the SSRF vulnerability.

3

What versions of Payload are affected by CVE-2026-27567?

CVE-2026-27567 affects all versions of Payload prior to 3.75.0.

4

What type of vulnerability is CVE-2026-27567?

CVE-2026-27567 is a Server-Side Request Forgery (SSRF) vulnerability.

5

Can CVE-2026-27567 lead to data compromise?

Yes, CVE-2026-27567 can potentially allow an attacker to access internal resources, leading to data compromise.

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