VulnerabilityAnalyzed

CVE-2026-30863

This allows an attacker to use a validly signed JWT issued for a different application to authenticate as any user on the target Parse Server.

CRITICAL 9.3EPSS 0.53%

Does this matter?

High impact if exploited, but EPSS currently rates exploitation as unlikely (0.53%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.10 and 9.5.0-alpha.11, the Google, Apple, and Facebook authentication adapters use JWT verification to validate identity tokens. When the adapter's audience configuration option is not set (clientId for Google/Apple, appIds for Facebook), JWT verification silently skips audience claim validation. This allows an attacker to use a validly signed JWT issued for a different application to authenticate as any user on the target Parse Server. This issue has been patched in versions 8.6.10 and 9.5.0-alpha.11.

CVSS 4.0: 9.3 CRITICALCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
EPSS: 0.53% probability · 43th percentile
CISA KEV: Not listed
Weakness: CWE-287, CWE-863
Affected: parseplatform/parse-server
Source: security-advisories@github.com

References

https://github.com/parse-community/parse-server/security/advisories/GHSA-x6fw-778m-wr9vVendor Advisory

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.