What is CVE-2025-68150?

CVE-2025-68150 is a high-severity server-side request forgery (SSRF) vulnerability in parse-server (npm), affecting versions < 8.6.2. It is fixed in 8.6.2, 9.1.1-alpha.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of parse-server are affected by CVE-2025-68150?

parse-server (npm) versions < 8.6.2 is affected.

Is there a fix for CVE-2025-68150?

Yes. CVE-2025-68150 is fixed in 8.6.2, 9.1.1-alpha.1. Upgrade to this version or later.

Is CVE-2025-68150 exploitable, and should I be worried?

Whether CVE-2025-68150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-68150 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-68150?

Upgrade: parse-server to 8.6.2 or later, parse-server to 9.1.1-alpha.1 or later.

CVE-2025-68150 in parse-server | Intelligent Application Security

Q: Which versions of parse-server are affected by CVE-2025-68150?

parse-server (npm) versions < 8.6.2 is affected.

Q: Is there a fix for CVE-2025-68150?

Yes. CVE-2025-68150 is fixed in 8.6.2, 9.1.1-alpha.1. Upgrade to this version or later.

Q: Is CVE-2025-68150 exploitable, and should I be worried?

Whether CVE-2025-68150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-68150 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-68150?

Upgrade: parse-server to 8.6.2 or later, parse-server to 9.1.1-alpha.1 or later.

Summary

Workarounds

None.

Impact

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.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

parse-server (< 8.6.2) parse-server (>= 9.0.0, < 9.1.1-alpha.1)

Security releases

parse-server → 8.6.2 (npm) parse-server → 9.1.1-alpha.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Fixed by hardcoding the Instagram Graph API URL https://graph.instagram.com and ignoring client-provided apiURL values.

Frequently Asked Questions

What is CVE-2025-68150? CVE-2025-68150 is a high-severity server-side request forgery (SSRF) vulnerability in parse-server (npm), affecting versions < 8.6.2. It is fixed in 8.6.2, 9.1.1-alpha.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of parse-server are affected by CVE-2025-68150? parse-server (npm) versions < 8.6.2 is affected.
Is there a fix for CVE-2025-68150? Yes. CVE-2025-68150 is fixed in 8.6.2, 9.1.1-alpha.1. Upgrade to this version or later.
Is CVE-2025-68150 exploitable, and should I be worried? Whether CVE-2025-68150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-68150 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-68150?
- Upgrade parse-server to 8.6.2 or later
- Upgrade parse-server to 9.1.1-alpha.1 or later

Other vulnerabilities in parse-server

CVE-IDSeverityPackage summary

GHSA-97PR-9HGG-3P8RLowparse-server: parse-server: LiveQuery discloses object data to a subscriber across an ACL read-access change CVE-2026-55778Lowparse-server: parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist CVE-2026-53726Mediumparse-server: parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL CVE-2026-53725Mediumparse-server: parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields…CVE-2026-53724Lowparse-server: parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist