CVE-2026-30925: Parse Server affected by Regular Expression Denial of Service (ReDoS) via `$regex` query in LiveQuery

Published Mar 9, 2026
·
Updated

Impact

A malicious client can subscribe to a LiveQuery with a crafted $regex pattern that causes catastrophic backtracking, blocking the Node.js event loop. This makes the entire Parse Server unresponsive, affecting all clients. Any Parse Server deployment with LiveQuery enabled is affected. The attacker only needs the application ID and JavaScript key, both of which are public in client-side apps.

This only affects LiveQuery subscription matching, which evaluates regex in JavaScript on the Node.js event loop. Normal REST and GraphQL queries are not affected because their regex is evaluated by the database engine.

Patches

Regex evaluation in LiveQuery subscription matching now runs in an isolated VM context with a configurable timeout via a new Parse Server option liveQuery.regexTimeout, with defaults 100 ms. A regex that exceeds the timeout is treated as non-matching.

The protection adds approximately 50 microseconds of overhead per regex evaluation. For most applications this is negligible, but it can add up if there is a very large number of LiveQuery subscriptions that use $regex on the same class. For example, 10,000 concurrent regex subscriptions would add approximately 500ms of processing time per object save event on that class. Set liveQuery.regexTimeout: 0 to disable the protection and use native regex evaluation without overhead.

Workarounds

Use the beforeSubscribe Cloud Code hook to reject any LiveQuery subscription that contains a $regex operator. Note that this also blocks the LiveQuery startsWith, endsWith, and contains query methods, as they use $regex internally.

js // Repeat for each class that is used with LiveQuery Parse.Cloud.beforeSubscribe('MyClass', request => { const where = request.query.where || {}; for (const value of Object.values(where)) { if (value?.$regex) { throw new Parse.Error(Parse.Error.OPERATIONFORBIDDEN, '$regex not allowed in LiveQuery subscriptions'); } } });

References

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-mf3j-86qx-cq5j - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.14 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.11

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.0-alpha.14 and 8.6.11, a malicious client can subscribe to a LiveQuery with a crafted $regex pattern that causes catastrophic backtracking, blocking the Node.js event loop. This makes the entire Parse Server unresponsive, affecting all clients. Any Parse Server deployment with LiveQuery enabled is affected. The attacker only needs the application ID and JavaScript key, both of which are public in client-side apps. This only affects LiveQuery subscription matching, which evaluates regex in JavaScript on the Node.js event loop. Normal REST and GraphQL queries are not affected because their regex is evaluated by the database engine. This vulnerability is fixed in 9.5.0-alpha.14 and 8.6.11.

MITRE

Affected Software

18 affected componentsFixes available
npm/parse-server<9.5.0-alpha.14, <8.6.11
npm/parse-server<8.6.11
8.6.11
npm/parse-server>=9.0.0-alpha.1<9.5.0-alpha.14
9.5.0-alpha.14
parseplatform Parse-server Node.js<8.6.11
parseplatform Parse-server Node.js>=9.0.0<9.5.0
parseplatform Parse-server Node.js=9.5.0-alpha1
parseplatform Parse-server Node.js=9.5.0-alpha10
parseplatform Parse-server Node.js=9.5.0-alpha11
parseplatform Parse-server Node.js=9.5.0-alpha12
parseplatform Parse-server Node.js=9.5.0-alpha13
parseplatform Parse-server Node.js=9.5.0-alpha2
parseplatform Parse-server Node.js=9.5.0-alpha3
parseplatform Parse-server Node.js=9.5.0-alpha4
parseplatform Parse-server Node.js=9.5.0-alpha5
parseplatform Parse-server Node.js=9.5.0-alpha6
parseplatform Parse-server Node.js=9.5.0-alpha7
parseplatform Parse-server Node.js=9.5.0-alpha8
parseplatform Parse-server Node.js=9.5.0-alpha9

Event History

Mar 9, 2026
CVE Published
via MITRE·11:01 PM
Data Sourced
via MITRE·11:01 PM
DescriptionWeakness
Mar 10, 2026
Advisory Published
via GitHub·12:57 AM
Data Sourced
via GitHub·12:57 AM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·05:40 PM
RemedyDescriptionSeverityWeaknessAffected Software
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-30925?

CVE-2026-30925 is considered a high severity vulnerability due to its potential to cause denial of service in Parse Server.

2

How do I fix CVE-2026-30925?

To mitigate CVE-2026-30925, update Parse Server to version 8.6.11 or 9.5.0-alpha.14 or later.

3

Which versions of Parse Server are affected by CVE-2026-30925?

CVE-2026-30925 affects Parse Server versions prior to 8.6.11 and versions from 9.0.0-alpha.1 up to 9.5.0-alpha.14.

4

Can CVE-2026-30925 affect my production environment?

Yes, CVE-2026-30925 can cause performance issues and potential downtime in production environments using affected versions of Parse Server.

5

What type of attack does CVE-2026-30925 allow?

CVE-2026-30925 allows attackers to exploit regular expressions in LiveQuery, resulting in denial of service through catastrophic backtracking.

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