Internal service data disclosure via unchecked redirects
Published Feb 24, 2026 · Updated Feb 24, 2026
SSRF in Payload before 3.75.0 allows remote authenticated users to retrieve internal service responses through external file uploads. The getExternalFile path used safeFetch only for the initial URL, while the HTTP client automatically followed redirects without revalidating each destination. Exploitation requires an upload-enabled collection and create access to it; successful requests can read internal service content through the application.
Summary
What happened
SSRF in Payload before 3.75.0 allows remote authenticated users to retrieve internal service responses through external file uploads. The getExternalFile path used safeFetch only for the initial URL, while the HTTP client automatically followed redirects without revalidating each destination. Exploitation requires an upload-enabled collection and create access to it; successful requests can read internal service content through the application.
The record
- CVE
- CVE-2026-27567
- Published
- Feb 24, 2026
- Updated
- Feb 24, 2026
- Vendor
- Payload CMS
- Product
- Payload
- Classifications
- CWE-918
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 24, 2026CVE publishedPublication date reported by the CVE source.
- Feb 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.75.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo