CVE-2025-53364

Description

### Impact The Parse Server GraphQL API previously allowed public access to the GraphQL schema without requiring a session token or the master key. While schema introspection reveals only metadata and not actual data, this metadata can still expand the potential attack surface. ### Patches The issue has been addressed by requiring the master key for schema introspection. Additionally, a new Parse Server configuration option, `graphQLPublicIntrospection`, has been introduced. This option allows developers to re-enable public schema introspection if their application relies on it. However, it is strongly recommended to use this option only temporarily and to update the application to function without depending on public introspection. ### Workarounds None available. ### References - GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-48q3-prgv-gm4w - Fix for Parse Server 7: https://github.com/parse-community/parse-server/pull/9820 - Fix for Parse Server 8: https://github.com/parse-community/parse-server/pull/9819

How to fix CVE-2025-53364

To remediate CVE-2025-53364, upgrade the affected package to a fixed version below.

• —upgrade to 8.2.2 or later
• —upgrade to 8.2.2 or later

Is CVE-2025-53364 being exploited?

Low — EPSS is 1.0%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• >= 5.3.0, < 8.2.2
• >= 8.0.0, < 8.2.2

CVSS scores

References (5)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2025-53364
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/pull/9819
• WEBgithub.com/parse-community/parse-server/pull/9820