CVE-2026-34373: Parse Server: GraphQL API endpoint ignores CORS origin restriction

Published Mar 30, 2026
·
Updated

Impact

The GraphQL API endpoint does not respect the allowOrigin server option and unconditionally allows cross-origin requests from any website. This bypasses origin restrictions that operators configure to control which websites can interact with the Parse Server API. The REST API correctly enforces the configured allowOrigin restriction.

Patches

The GraphQL API endpoint now uses the same CORS middleware as the REST API, ensuring the allowOrigin and allowHeaders server options are consistently enforced across all endpoints.

Workarounds

There is no known workaround other than upgrading.

Resources

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-q3p6-g7c4-829c - Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10334 - Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10335

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.66 and 9.7.0-alpha.10, the GraphQL API endpoint does not respect the allowOrigin server option and unconditionally allows cross-origin requests from any website. This bypasses origin restrictions that operators configure to control which websites can interact with the Parse Server API. The REST API correctly enforces the configured allowOrigin restriction. This issue has been patched in versions 8.6.66 and 9.7.0-alpha.10.

MITRE

Affected Software

13 affected componentsFixes available
npm/parse-server>=3.5.0<8.6.66
8.6.66
npm/parse-server>=9.0.0<9.7.0-alpha.10
9.7.0-alpha.10
parseplatform Parse-server Node.js>=3.5.0<8.6.66
parseplatform Parse-server Node.js>=9.0.0<9.7.0
parseplatform Parse-server Node.js=9.7.0-alpha1
parseplatform Parse-server Node.js=9.7.0-alpha2
parseplatform Parse-server Node.js=9.7.0-alpha3
parseplatform Parse-server Node.js=9.7.0-alpha4
parseplatform Parse-server Node.js=9.7.0-alpha5
parseplatform Parse-server Node.js=9.7.0-alpha6
parseplatform Parse-server Node.js=9.7.0-alpha7
parseplatform Parse-server Node.js=9.7.0-alpha8
parseplatform Parse-server Node.js=9.7.0-alpha9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 8.6.66
  2. Upgrade

    Upgrade npm/parse-server to a version that resolves this vulnerability.

    Fixed in 9.7.0-alpha.10
  3. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 8.6.66
  4. Upgrade

    Upgrade Parse Server to a version that resolves this vulnerability.

    Fixed in 9.7.0-alpha.10

Event History

Mar 30, 2026
Advisory Published
via GitHub·06:05 PM
Data Sourced
via GitHub·06:05 PM
DescriptionWeaknessAffected Software
Mar 31, 2026
CVE Published
via MITRE·02:38 PM
Data Sourced
via MITRE·02:38 PM
DescriptionWeakness
Data Sourced
via NVD·03:16 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-34373?

CVE-2026-34373 is considered a high-severity vulnerability due to its potential for cross-origin request forgery.

2

How do I fix CVE-2026-34373?

To fix CVE-2026-34373, upgrade to Parse Server version 8.6.66 or 9.7.0-alpha.10.

3

What type of vulnerability is CVE-2026-34373?

CVE-2026-34373 is a cross-origin resource sharing (CORS) vulnerability affecting the GraphQL API.

4

What systems are affected by CVE-2026-34373?

CVE-2026-34373 affects npm packages of Parse Server versions between 3.5.0 and 8.6.66, as well as versions from 9.0.0 to 9.7.0-alpha.10.

5

How does CVE-2026-34373 impact security?

CVE-2026-34373 compromises security by allowing unauthorized cross-origin requests, potentially enabling data theft or manipulation.

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