# CVE-2026-27567: Payload Server-Side Request Forgery in external file uploads

Source: https://junglewise.ai/threats/cve-2026-27567-payload-server-side-request-forgery-in-external-file-uploads  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-24. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-27567 · Severity: low · CVSS 3.1 · Published 2026-02-24

Payload is a popular Node.js headless CMS used for managing and serving content through APIs. The vulnerability allows authenticated users with upload permissions to access internal network resources by exploiting insufficient validation of HTTP redirects during external file uploads, potentially exposing sensitive internal services and data.

Technologies: [payload (npm)](https://junglewise.ai/threats/technologies/payload). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-27567 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-27567 being exploited in the wild.

**How severe is CVE-2026-27567?** Low severity, with a CVSS score of 3.1, published 24 February 2026.

**Which products and versions are affected?** payload (npm) SEMVER:introduced=0,fixed=3.75.0.

**Is there a fix for CVE-2026-27567?** Yes. payload (npm): upgrade to 3.75.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-27567 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-27567?** Check whether you run payload (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- payload (npm): upgrade to 3.75.0 or later

  ```sh
  npm install payload@3.75.0
  ```


## Technical details

Payload versions prior to v3.75.0 contain a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in the external file upload functionality. The vulnerability stems from insufficient validation of HTTP redirects when processing external URLs for file uploads. An authenticated user with write permissions on an upload-enabled collection can craft a malicious URL that exploits redirect handling to access internal network resources. The attack requires authentication and collection-level create access, but no user interaction. Successful exploitation allows retrieval of response content from internal services, potentially exposing sensitive data. The vulnerability has been patched in v3.75.0; users can also mitigate by disabling external file uploads or restricting collection access to trusted users.

## Affected products

- Payload CMS Payload < 3.75.0

## Identifiers

- CVE-2026-27567
- GHSA-hhfx-5x8j-f5f6

## Timeline

- 2026-02-24: disclosed
- 2026-02-24: patched: v3.75.0 released

## References

- [https://github.com/payloadcms/payload/security/advisories/GHSA-hhfx-5x8j-f5f6](https://github.com/payloadcms/payload/security/advisories/GHSA-hhfx-5x8j-f5f6)

## Related threats

- [Payload CMS stored XSS in XML upload handling](https://junglewise.ai/threats/cve-2026-105868-payload-is-a-free-and-open-source-headless-content-management)
- [Payload CMS account lockout denial of service](https://junglewise.ai/threats/cve-2026-105866-payload-is-a-free-and-open-source-headless-content-management)
- [Payload CMS path traversal in file deletion](https://junglewise.ai/threats/cve-2026-105865-payload-is-a-free-and-open-source-headless-content-management)
- [Payload CMS authentication token tampering via reserved JWT fields](https://junglewise.ai/threats/cve-2026-105863-payload-is-a-free-and-open-source-headless-content-management)
- [Payload CMS stored XSS in SVG upload sanitization](https://junglewise.ai/threats/cve-2026-105862-payload-is-a-free-and-open-source-headless-content-management)