CVE-2026-34746
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPayload is a free and open source headless content management system. Prior to version 3.79.1, an authenticated Server-Side Request Forgery (SSRF) vulnerability exists in the upload functionality. Authenticated users with create or update access to an upload-enabled collection could cause the server to make outbound HTTP requests to arbitrary URLs. This issue has been patched in version 3.79.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an authenticated Server-Side Request Forgery (SSRF) vulnerability in Payload CMS's upload functionality. Authenticated users with create or update permissions on upload-enabled collections can cause the server to make outbound HTTP requests to arbitrary URLs, potentially allowing internal service enumeration or data exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.79.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Payload CMS installationCheck your application directories and package.json for @payloadcms/{} dependencies, or query the /api/{} endpoint of your Payload CMS instanceAffected if Payload CMS is not present in the environment
-
Determine installed Payload CMS versionRun 'npm list @payloadcms/{}' in the project directory, check package.json, or query the /api/{} endpoint with a GET request to retrieve version informationAffected if The installed version is lower than 3.79.1
-
Identify upload-enabled collectionsReview your Payload CMS collection configurations in collections/{} or the database. Look for collections with upload: true in their config, or check the payload-collections metadataAffected if No collections have upload functionality enabled, the SSRF cannot be triggered
-
Check collection permissions for create/updateExamine the access control settings in your collection configs or navigate to Settings > Collections > [collection] > Access Control in the admin panel. Verify which roles or users have create or update permissionsAffected if Authenticated users with create or update permissions exist on upload-enabled collections, they can trigger the SSRF vulnerability
You are affected if you are running Payload CMS version lower than 3.79.1 AND have upload-enabled collections accessible to authenticated users with create or update permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.79.1
Upgrade Payload CMS to version 3.79.1 or later to apply the patch. Restrict upload-enabled collection permissions to only trusted administrative users until the upgrade is completed.
Payload version 3.79.1
- Verify current Payload version by checking package.json or running npm list payload
- Update payload version in package.json to ^3.79.1 or the latest stable release
- Run npm install or yarn install to update dependencies
- Review the official Payload release notes at github.com/payloadcms/payload/releases for any migration requirements
- Test the application functionality, particularly upload features, in a staging environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data