CVE-2025-68150: parse-server · Server-Side Request Forgery (SSRF)
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 8.6.2 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.6.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade parse-server to 8.6.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmparse-serverpkg:npm/parse-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations using parse-server with Instagram authentication should immediately upgrade to parse-server versions 8.6.2 or later, or 9.1.1-alpha.1 and above, where the vulnerability is fixed by hardcoding the Instagram Graph API URL. Since no workarounds exist, patching is the primary mitigation. Additionally, organizations should audit their parse-server configurations to ensure no custom apiURL parameters are accepted or processed. Implement network-level controls to restrict outbound HTTP requests from backend servers to only trusted endpoints, minimizing SSRF impact. Employ web application firewalls (WAFs) with SSRF detection rules to monitor and block suspicious request patterns. Conduct internal penetration testing focusing on SSRF vectors to identify any residual risks. Monitor logs for unusual outbound requests or authentication anomalies related to Instagram login flows. Finally, educate developers about secure handling of third-party authentication parameters to prevent similar issues in the future.
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.