CVE-2026-31828: Parse Server has an LDAP injection via unsanitized user input in DN and group filter construction

Published Mar 10, 2026
·
Updated

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.

Patches

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

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

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.13 and 8.6.26, 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. This vulnerability is fixed in 9.5.2-alpha.13 and 8.6.26.

MITRE

Affected Software

17 affected componentsFixes available
npm/parse-server<9.5.2-alpha.13, <8.6.26
npm/parse-server<8.6.26
8.6.26
npm/parse-server>=9.0.0-alpha.1<9.5.2-alpha.13
9.5.2-alpha.13
parseplatform Parse-server Node.js<8.6.26
parseplatform Parse-server Node.js>=9.0.0<9.5.2
parseplatform Parse-server Node.js=9.5.2-alpha1
parseplatform Parse-server Node.js=9.5.2-alpha10
parseplatform Parse-server Node.js=9.5.2-alpha11
parseplatform Parse-server Node.js=9.5.2-alpha12
parseplatform Parse-server Node.js=9.5.2-alpha2
parseplatform Parse-server Node.js=9.5.2-alpha3
parseplatform Parse-server Node.js=9.5.2-alpha4
parseplatform Parse-server Node.js=9.5.2-alpha5
parseplatform Parse-server Node.js=9.5.2-alpha6
parseplatform Parse-server Node.js=9.5.2-alpha7
parseplatform Parse-server Node.js=9.5.2-alpha8
parseplatform Parse-server Node.js=9.5.2-alpha9

Event History

Mar 10, 2026
CVE Published
via MITRE·09:41 PM
Data Sourced
via MITRE·09:41 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 11, 2026
Advisory Published
via GitHub·12:23 AM
Data Sourced
via GitHub·12:23 AM
DescriptionWeaknessAffected Software
Jul 22, 58183
Event
via NVD·03:29 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-31828?

CVE-2026-31828 is considered a critical vulnerability due to the possibility of LDAP injection attacks.

2

How do I fix CVE-2026-31828?

To address CVE-2026-31828, you should upgrade to Parse Server version 8.6.27 or later, or 9.5.2-alpha.14 or later.

3

What types of attacks can CVE-2026-31828 facilitate?

CVE-2026-31828 can potentially be exploited for LDAP injection attacks, allowing an attacker to manipulate the LDAP queries.

4

What affected software versions are related to CVE-2026-31828?

CVE-2026-31828 impacts Parse Server versions up to and including 8.6.26 and 9.5.2-alpha.13.

5

Is user input protected against CVE-2026-31828?

No, the vulnerability arises from unsanitized user input in the Distinguished Name (DN) and group filter construction.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203