CVE-2026-33538: Parse Server: Denial of service via unindexed database query for unconfigured auth providers

Published Mar 24, 2026
·
Updated

Impact

An unauthenticated attacker can cause Denial of Service by sending authentication requests with arbitrary, unconfigured provider names. The server executes a database query for each unconfigured provider before rejecting the request, and since no database index exists for unconfigured providers, each request triggers a full collection scan on the user database. This can be parallelized to saturate database resources.

Patches

The fix validates that an authentication provider is configured before executing any database query. Requests with unconfigured providers are now rejected immediately without querying the database.

Workarounds

There is no known workaround other than upgrading.

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.58 and 9.6.0-alpha.52, an unauthenticated attacker can cause denial of service by sending authentication requests with arbitrary, unconfigured provider names. The server executes a database query for each unconfigured provider before rejecting the request, and since no database index exists for unconfigured providers, each request triggers a full collection scan on the user database. This can be parallelized to saturate database resources. This issue has been patched in versions 8.6.58 and 9.6.0-alpha.52.

MITRE

Affected Software

56 affected componentsFixes available
Parse Platform Parse Server<8.6.58, <9.6.0-alpha.52
npm/parse-server<8.6.58
8.6.58
npm/parse-server>=9.0.0<9.6.0-alpha.52
9.6.0-alpha.52
parseplatform Parse-server Node.js<8.6.58
parseplatform Parse-server Node.js>=9.0.0<9.6.0
parseplatform Parse-server Node.js=9.6.0-alpha1
parseplatform Parse-server Node.js=9.6.0-alpha10
parseplatform Parse-server Node.js=9.6.0-alpha11
parseplatform Parse-server Node.js=9.6.0-alpha12
parseplatform Parse-server Node.js=9.6.0-alpha13
parseplatform Parse-server Node.js=9.6.0-alpha14
parseplatform Parse-server Node.js=9.6.0-alpha15
parseplatform Parse-server Node.js=9.6.0-alpha16
parseplatform Parse-server Node.js=9.6.0-alpha17
parseplatform Parse-server Node.js=9.6.0-alpha18
parseplatform Parse-server Node.js=9.6.0-alpha19
parseplatform Parse-server Node.js=9.6.0-alpha2
parseplatform Parse-server Node.js=9.6.0-alpha20
parseplatform Parse-server Node.js=9.6.0-alpha21
parseplatform Parse-server Node.js=9.6.0-alpha22
parseplatform Parse-server Node.js=9.6.0-alpha23
parseplatform Parse-server Node.js=9.6.0-alpha24
parseplatform Parse-server Node.js=9.6.0-alpha25
parseplatform Parse-server Node.js=9.6.0-alpha26
parseplatform Parse-server Node.js=9.6.0-alpha27
parseplatform Parse-server Node.js=9.6.0-alpha28
parseplatform Parse-server Node.js=9.6.0-alpha29
parseplatform Parse-server Node.js=9.6.0-alpha3
parseplatform Parse-server Node.js=9.6.0-alpha30
parseplatform Parse-server Node.js=9.6.0-alpha31
parseplatform Parse-server Node.js=9.6.0-alpha32
parseplatform Parse-server Node.js=9.6.0-alpha33
parseplatform Parse-server Node.js=9.6.0-alpha34
parseplatform Parse-server Node.js=9.6.0-alpha35
parseplatform Parse-server Node.js=9.6.0-alpha36
parseplatform Parse-server Node.js=9.6.0-alpha37
parseplatform Parse-server Node.js=9.6.0-alpha38
parseplatform Parse-server Node.js=9.6.0-alpha39
parseplatform Parse-server Node.js=9.6.0-alpha4
parseplatform Parse-server Node.js=9.6.0-alpha40
parseplatform Parse-server Node.js=9.6.0-alpha41
parseplatform Parse-server Node.js=9.6.0-alpha42
parseplatform Parse-server Node.js=9.6.0-alpha43
parseplatform Parse-server Node.js=9.6.0-alpha44
parseplatform Parse-server Node.js=9.6.0-alpha45
parseplatform Parse-server Node.js=9.6.0-alpha46
parseplatform Parse-server Node.js=9.6.0-alpha47
parseplatform Parse-server Node.js=9.6.0-alpha48
parseplatform Parse-server Node.js=9.6.0-alpha49
parseplatform Parse-server Node.js=9.6.0-alpha5
parseplatform Parse-server Node.js=9.6.0-alpha50
parseplatform Parse-server Node.js=9.6.0-alpha51
parseplatform Parse-server Node.js=9.6.0-alpha6
parseplatform Parse-server Node.js=9.6.0-alpha7
parseplatform Parse-server Node.js=9.6.0-alpha8
parseplatform Parse-server Node.js=9.6.0-alpha9

Event History

Mar 24, 2026
CVE Published
via MITRE·06:24 PM
Data Sourced
via MITRE·06:24 PM
DescriptionWeakness
Advisory Published
via GitHub·07:11 PM
Data Sourced
via GitHub·07:11 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 22, 58202
Event
via FIRST·03:46 PM
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-33538?

CVE-2026-33538 is classified as a denial of service vulnerability that can be exploited by unauthenticated attackers.

2

How does CVE-2026-33538 affect Parse Server?

CVE-2026-33538 allows attackers to cause a denial of service by executing unindexed database queries when specific authentication providers are not configured.

3

How do I fix CVE-2026-33538?

To fix CVE-2026-33538, upgrade your Parse Server to versions 8.6.58 or 9.6.0-alpha.52 or later.

4

What are the affected versions for CVE-2026-33538?

CVE-2026-33538 affects Parse Server versions prior to 8.6.58 and 9.6.0-alpha.52.

5

Can CVE-2026-33538 be exploited remotely?

Yes, CVE-2026-33538 can be exploited remotely by unauthenticated users.

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