Medium SSRF

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

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.

Published Feb 24, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+5
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.42%

ahead of 35% of scored CVEs · Oct 14, 2026

Affects

@payloadcms

Payload

CVSS base

4.8

Medium · 3 source(s)

Prioritization reference: 6.5 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)
Documented mitigation — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (@payloadcms Payload).
Apply the fixed version or the patch documented under Remediation.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
@payloadcms	Payload	< 3.75.0	Vulnerable	NIST National Vulnerability Database
@payloadcms	Payload	version < 3.75.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.5	CVSS 3.1	Medium	1.2	5.2	security-advisories@github.com via NIST National Vulnerability Database
6.5	CVSS 3.1	Medium	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP
4.8	CVSS 3.1	Medium	1.7	2.7	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 6.5 (security-advisories@github.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.42%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.

web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

2026
Affected products added · payloadcms/payload
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 4.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Feb 24, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

github.com/payloadcms/payload/security/advisories/GHSA-hhfx-5x8j-f5f6
Mitigation, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
github.com/payloadcms/payload/commit/1041bb6
Patch, x_refsource_MISC, NIST National Vulnerability Database
github.com/payloadcms/payload/releases/tag/v3.75.0
Product, Release Notes, x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

@payloadcms
every CVE for this vendor

SSRF
same class

CWE-918
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-106100 Payload: Field-level write access bypass in Payload on MongoDB 9d
Medium CVE-2026-105867 Payload: Client uploads could overwrite S3 objects 9d
High CVE-2026-105868 Payload: Uploaded XML files could execute same-origin JavaScript 9d
Medium CVE-2026-105864 Payload: Cross-tenant create in @payloadcms/plugin-multi-tenant 9d
High CVE-2026-105862 Payload: Bypassed sanitization of user uploaded SVGs 9d
High CVE-2026-105866 Payload: Unauthenticated account-lockout denial of service 9d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-27567 is "Payload has Server-Side Request Forgery (SSRF) in External File URL Uploads", rated Medium. It affects Payload (@payloadcms); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.8 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.