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.
CVE-2026-30863
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
March 7, 2026
Last Modified
June 17, 2026
Advisory Details (1)
Auto-updated Sep 14, 2026JWT audience validation bypass in Google, Apple, and Facebook authentication adapters · Advisory · parse-community/parse-server · GitHub
https://github.com/parse-community/parse-server/security/advisories/GHSA-x6fw-778m-wr9vAffected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| parse-server | — | 8.6.10 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 30× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 23:29 UTCOSV refresh
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
Show 38 moreShow fewer
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:17 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:12 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:40 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 22:29 UTCEG score recompute
- 2026-08-11 05:19 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 17:40 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 07:51 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 19:17 UTCEG score recompute
- 2026-08-06 20:22 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:20 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 01:45 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 18:32 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:49 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
- CVE-2006-5268EG 10.0EPSS p94HIGH
- CVE-2007-5391EG 10.0EPSS p90HIGH
- CVE-2007-5383EG 10.0EPSS p90HIGH
- CVE-2007-5006EG 10.0EPSS p97HIGH
- CVE-2007-5057EG 10.0EPSS p91HIGH
- CVE-2007-4747EG 10.0HIGH
- CVE-2007-4548EG 10.0EPSS p90HIGH
- CVE-2007-2719EG 10.0EPSS p91HIGH
- CVE-2007-1160EG 10.0HIGH
- CVE-2007-1062EG 10.0EPSS p90HIGH
Frequently asked(5)
What is CVE-2026-30863?
When was CVE-2026-30863 disclosed?
Is CVE-2026-30863 actively exploited?
What is the CVSS score of CVE-2026-30863?
How do I remediate CVE-2026-30863?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-30863
Is Your Infrastructure Affected by CVE-2026-30863?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.