What is CVE-2022-39396?

CVE-2022-39396 is a critical-severity security vulnerability in parse-server (npm), affecting versions < 4.10.18. It is fixed in 4.10.18, 5.3.1.

How severe is CVE-2022-39396?

CVE-2022-39396 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of parse-server are affected by CVE-2022-39396?

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

Is there a fix for CVE-2022-39396?

Yes. CVE-2022-39396 is fixed in 4.10.18, 5.3.1. Upgrade to this version or later.

Is CVE-2022-39396 exploitable, and should I be worried?

Whether CVE-2022-39396 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-2022-39396 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-2022-39396?

Upgrade: parse-server to 4.10.18 or later, parse-server to 5.3.1 or later.

CVE-2022-39396 in parse-server | Intelligent Application Security

Q: How severe is CVE-2022-39396?

CVE-2022-39396 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of parse-server are affected by CVE-2022-39396?

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

Q: Is there a fix for CVE-2022-39396?

Yes. CVE-2022-39396 is fixed in 4.10.18, 5.3.1. Upgrade to this version or later.

Q: Is CVE-2022-39396 exploitable, and should I be worried?

Whether CVE-2022-39396 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-2022-39396 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-2022-39396?

Upgrade: parse-server to 4.10.18 or later, parse-server to 5.3.1 or later.

Summary

Workarounds

Disable remote code execution through the MongoDB BSON parser.

Collaborators

Mikhail Shcherbakov (KTH), Cristian-Alexandru Staicu (CISPA) and Musard Balliu (KTH) working with Trend Micro Zero Day Initiative

References

https://github.com/parse-community/parse-server/security/advisories/GHSA-prm5-8g2m-24gg

Impact

An attacker can use this prototype pollution sink to trigger a remote code execution through the MongoDB BSON parser.

CVE-2022-39396 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.10.18, 5.3.1); upgrading removes the vulnerable code path.

Affected versions

parse-server (< 4.10.18) parse-server (>= 5.0.0, < 5.3.1)

Security releases

parse-server → 4.10.18 (npm) parse-server → 5.3.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

Prevent prototype pollution in MongoDB database adapter.

Frequently Asked Questions

What is CVE-2022-39396? CVE-2022-39396 is a critical-severity security vulnerability in parse-server (npm), affecting versions < 4.10.18. It is fixed in 4.10.18, 5.3.1.
How severe is CVE-2022-39396? CVE-2022-39396 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of parse-server are affected by CVE-2022-39396? parse-server (npm) versions < 4.10.18 is affected.
Is there a fix for CVE-2022-39396? Yes. CVE-2022-39396 is fixed in 4.10.18, 5.3.1. Upgrade to this version or later.
Is CVE-2022-39396 exploitable, and should I be worried? Whether CVE-2022-39396 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-2022-39396 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-2022-39396?
- Upgrade parse-server to 4.10.18 or later
- Upgrade parse-server to 5.3.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