{"answers":{"affected":"5 open source packages ship an affected version, including parse-server and parse. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68150 in the wild and no public exploit code.","fix":"Upgrade parse-server to a fixed version for your release line: 8.6.2 or 9.1.1-alpha.1.","what":"CVE-2025-68150 is a high-severity server-side request forgery vulnerability in Parseplatform Parse-Server, published on 16 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68150 and fix it if it is affected.\n\nWhat it is: CVE-2025-68150 is a high-severity server-side request forgery vulnerability in Parseplatform Parse-Server, published on 16 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68150 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- parse-server (npm): affected all versions; fixed in 8.6.2\n- parse-server (npm): affected all versions; fixed in 8.6.2\n- parse-server (npm): affected from 9.0.0; fixed in 9.1.1-alpha.1\n- parse-server (npm): affected from 9.0.0; fixed in 9.1.1-alpha.1\n- parse (Bitnami): affected all versions; fixed in 8.6.2, 9.1.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-2025-68150/ (Markdown: https://insights.sbomify.com/CVE-2025-68150/index.md)","id":"CVE-2025-68150","markdown":"https://insights.sbomify.com/CVE-2025-68150/index.md","name":"CVE-2025-68150","record":{"aliases":["BIT-parse-2025-68150","GHSA-3f5f-xgrj-97pf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Parse Server backend","requires_auth":"low_privilege","summary":"Attackers can exploit SSRF in the Instagram OAuth adapter to bypass authentication or access internal resources by specifying a malicious API URL.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"parse-server","vendor":"parseplatform"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.2 and 9.1.1-alpha.1, the Instagram authentication adapter allows clients to specify a custom API URL via the `apiURL` parameter in `authData`. This enables SSRF attacks and possibly authentication bypass if malicious endpoints return fake responses to validate unauthorized users. This is fixed in versions 8.6.2 and 9.1.1-alpha.1 by hardcoding the Instagram Graph API URL `https://graph.instagram.com` and ignoring client-provided `apiURL` values. No known workarounds are available.","ecosystems":["Bitnami","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":"Parse Server has Server-Side Request Forgery (SSRF) in Instagram OAuth Adapter","id":"CVE-2025-68150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"parseplatform:parse-server","products":["parseplatform:parse-server"],"type":"ssrf","year":"2025"},"n_packages":5,"n_references":3,"next":{"headline":"CoreDNS gRPC/HTTPS/HTTP3 servers lack resource limits, enabling DoS via unbounded connections and oversized messages","id":"CVE-2025-68151"},"packages":[{"ecosystem":"Bitnami","fixed":["8.6.2","9.1.1"],"introduced":["0","9.0.0"],"last_affected":[],"package":"parse","purl":"pkg:bitnami/parse","source":"BIT-parse-2025-68150"},{"ecosystem":"npm","fixed":["8.6.2"],"introduced":["0"],"last_affected":[],"package":"parse-server","purl":null,"source":"GHSA-3f5f-xgrj-97pf"},{"ecosystem":"npm","fixed":["8.6.2"],"introduced":["0"],"last_affected":[],"package":"parse-server","purl":"pkg:npm/parse-server","source":"GHSA-3f5f-xgrj-97pf"},{"ecosystem":"npm","fixed":["9.1.1-alpha.1"],"introduced":["9.0.0"],"last_affected":[],"package":"parse-server","purl":null,"source":"GHSA-3f5f-xgrj-97pf"},{"ecosystem":"npm","fixed":["9.1.1-alpha.1"],"introduced":["9.0.0"],"last_affected":[],"package":"parse-server","purl":"pkg:npm/parse-server","source":"GHSA-3f5f-xgrj-97pf"}],"prev":{"headline":"FreshRSS globally denies access to feed via proxy modifying to 429 Retry-After","id":"CVE-2025-68148"},"products":["parse-server"],"published":"2025-12-16","related":[{"cvss_score":10,"headline":"Parse Server role escalation and CLP bypass via direct `_Join` table write","id":"CVE-2026-30966","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":10,"headline":"Parse Server literalizeRegexPart SQL Injection","id":"CVE-2024-27298","kev_date_added":null,"published":"2024-03-01"},{"cvss_score":10,"headline":"Command Injection in Parse server","id":"CVE-2022-24760","kev_date_added":null,"published":"2022-03-11"},{"cvss_score":9.9,"headline":"Parse Server session token exfiltration via `redirectClassNameForKey` query parameter","id":"CVE-2026-30965","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":9.8,"headline":"Parse Server vulnerable to remote code execution via MongoDB BSON parser through prototype pollution","id":"CVE-2023-36475","kev_date_added":null,"published":"2023-06-28"},{"cvss_score":9.8,"headline":"Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser","id":"CVE-2022-39396","kev_date_added":null,"published":"2022-11-10"},{"cvss_score":9.3,"headline":"Parse Server: Account takeover via operator injection in authentication data identifier","id":"CVE-2026-32248","kev_date_added":null,"published":"2026-03-12"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"2025-12-17","vendors":["parse-community"]},"summary":"Attackers can exploit SSRF in the Instagram OAuth adapter to bypass authentication or access internal resources by specifying a malicious API URL.","url":"https://insights.sbomify.com/CVE-2025-68150/"}