What is CVE-2026-31828?

CVE-2026-31828 is a medium-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0-alpha.1, < 9.5.2-alpha.13. It is fixed in 9.5.2-alpha.13, 8.6.26.

Which versions of parse-server are affected by CVE-2026-31828?

parse-server (npm) versions >= 9.0.0-alpha.1, < 9.5.2-alpha.13 is affected.

Is there a fix for CVE-2026-31828?

Yes. CVE-2026-31828 is fixed in 9.5.2-alpha.13, 8.6.26. Upgrade to this version or later.

Is CVE-2026-31828 exploitable, and should I be worried?

Whether CVE-2026-31828 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-2026-31828 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-2026-31828?

Upgrade: parse-server to 9.5.2-alpha.13 or later, parse-server to 8.6.26 or later.

CVE-2026-31828 in parse-server | Intelligent Application Security

Q: Which versions of parse-server are affected by CVE-2026-31828?

parse-server (npm) versions >= 9.0.0-alpha.1, < 9.5.2-alpha.13 is affected.

Q: Is there a fix for CVE-2026-31828?

Yes. CVE-2026-31828 is fixed in 9.5.2-alpha.13, 8.6.26. Upgrade to this version or later.

Q: Is CVE-2026-31828 exploitable, and should I be worried?

Whether CVE-2026-31828 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-2026-31828 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-2026-31828?

Upgrade: parse-server to 9.5.2-alpha.13 or later, parse-server to 8.6.26 or later.

Summary

Workarounds

There is no known workaround.

References

GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-7m6r-fhh7-r47c
Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.13
Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.26

Impact

The LDAP authentication adapter is vulnerable to LDAP injection. User-supplied input (authData.id) is interpolated directly into LDAP Distinguished Names (DN) and group search filters without escaping special characters. This allows an attacker with valid LDAP credentials to manipulate the bind DN structure and to bypass group membership checks. This enables privilege escalation from any authenticated LDAP user to a member of any restricted group.

The vulnerability affects Parse Server deployments that use the LDAP authentication adapter with group-based access control.

Affected versions

parse-server (>= 9.0.0-alpha.1, < 9.5.2-alpha.13) parse-server (< 8.6.26)

Security releases

parse-server → 9.5.2-alpha.13 (npm) parse-server → 8.6.26 (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

The vulnerability is fixed by escaping user input before interpolation into DN strings (per RFC 4514) and LDAP filter strings (per RFC 4515).

Frequently Asked Questions

What is CVE-2026-31828? CVE-2026-31828 is a medium-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0-alpha.1, < 9.5.2-alpha.13. It is fixed in 9.5.2-alpha.13, 8.6.26.
Which versions of parse-server are affected by CVE-2026-31828? parse-server (npm) versions >= 9.0.0-alpha.1, < 9.5.2-alpha.13 is affected.
Is there a fix for CVE-2026-31828? Yes. CVE-2026-31828 is fixed in 9.5.2-alpha.13, 8.6.26. Upgrade to this version or later.
Is CVE-2026-31828 exploitable, and should I be worried? Whether CVE-2026-31828 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-2026-31828 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-2026-31828?
- Upgrade parse-server to 9.5.2-alpha.13 or later
- Upgrade parse-server to 8.6.26 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