{"answers":{"affected":"2 open source packages ship an affected version, including payload. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34746 in the wild and no public exploit code.","fix":"Upgrade payload to 3.79.1 or later.","what":"CVE-2026-34746 is a high-severity server-side request forgery vulnerability in payloadcms payload, published on 1 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34746 and fix it if it is affected.\n\nWhat it is: CVE-2026-34746 is a high-severity server-side request forgery vulnerability in payloadcms payload, published on 1 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34746 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- payload (npm): affected all versions; fixed in 3.79.1\n- payload (npm): affected all versions; fixed in 3.79.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34746/ (Markdown: https://insights.sbomify.com/CVE-2026-34746/index.md)","id":"CVE-2026-34746","markdown":"https://insights.sbomify.com/CVE-2026-34746/index.md","name":"CVE-2026-34746","record":{"aliases":["GHSA-6r7f-q7f5-wpx8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Payload CMS","requires_auth":"low_privilege","summary":"Authenticated users can trigger server-side requests to arbitrary URLs via upload functionality, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"payload","vendor":"payloadcms"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Payload 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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Payload has Authenticated SSRF via Upload Functionality","id":"CVE-2026-34746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Payload has an SQL Injection via Query Handling","id":"CVE-2026-34747"},"packages":[{"ecosystem":"npm","fixed":["3.79.1"],"introduced":["0"],"last_affected":[],"package":"payload","purl":null,"source":"GHSA-6r7f-q7f5-wpx8"},{"ecosystem":"npm","fixed":["3.79.1"],"introduced":["0"],"last_affected":[],"package":"payload","purl":"pkg:npm/payload","source":"GHSA-6r7f-q7f5-wpx8"}],"prev":{"headline":"Unauthenticated Path Traversal Arbitrary File Write in /api/uploadChunked/public","id":"CVE-2026-34745"},"products":["payload"],"published":"2026-04-01","related":[{"cvss_score":10,"headline":"Payload: RCE in Payload Form Builder","id":"CVE-2026-105857","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Payload: Unauthorized update to collection documents","id":"CVE-2026-105859","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.8,"headline":"Payload has an SQL Injection in JSON/RichText Queries on PostgreSQL/SQLite Adapters","id":"CVE-2026-25544","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":9.8,"headline":"Unrestricted Upload of File with Dangerous Type in Payload","id":"CVE-2022-27952","kev_date_added":null,"published":"2022-04-12"},{"cvss_score":9.3,"headline":"Payload: Field access control bypass on auth collections","id":"CVE-2026-105851","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.2,"headline":"Payload authentication token field handling issue","id":"CVE-2026-105863","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":9.1,"headline":"Payload has Unvalidated Input in Password Recovery Endpoints","id":"CVE-2026-34751","kev_date_added":null,"published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["payloadcms"]},"summary":"Authenticated users can trigger server-side requests to arbitrary URLs via upload functionality, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2026-34746/"}