CVE-2026-31800: Parseplatform Parse-server broken access control (CVSS 9.1)

Description

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.12 and 8.6.25, the _GraphQLConfig and _Audience internal classes can be read, modified, and deleted via the generic /classes/_GraphQLConfig and /classes/_Audience REST API routes without master key authentication. This bypasses the master key enforcement that exists on the dedicated /graphql-config and /push_audiences endpoints. An attacker can read, modify and delete GraphQL configuration and push audience data. This vulnerability is fixed in 9.5.2-alpha.12 and 8.6.25.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Parseplatform Parse-server9.5.2 · ≥ 9.0.0 < 9.5.2 · < 8.6.25

Remediation

Fixed in

Parseplatform Parse-server≥ 9.5.2

Patch & vendor advisories

https://github.com/parse-community/parse-server/security/advisories/GHSA-7xg7-rqf6-pw6c

References

https://github.com/parse-community/parse-server/releases/tag/8.6.25ProductRelease Notes
https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.12ProductRelease Notes
https://github.com/parse-community/parse-server/security/advisories/GHSA-7xg7-rqf6-pw6cPatchVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-31800 being actively exploited?

CVE-2026-31800 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.62%.

How severe is CVE-2026-31800?

CVE-2026-31800 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.62% probability of exploitation.

Which products are affected by CVE-2026-31800?

Affected products include Parseplatform Parse-server.

How do I fix CVE-2026-31800?

Upgrade affected software to a fixed version, for example Parseplatform Parse-server 9.5.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-31800 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo