Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-x6fw-778m-wr9v | Parse Server: JWT audience validation bypass in Google, Apple, and Facebook authentication adapters |
Tue, 10 Mar 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Parseplatform
Parseplatform parse-server |
|
| Weaknesses | CWE-863 | |
| CPEs | cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha10:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha1:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha2:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha3:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha4:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha5:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha6:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha7:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha8:*:*:*:node.js:*:* cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha9:*:*:*:node.js:*:* |
|
| Vendors & Products |
Parseplatform
Parseplatform parse-server |
|
| Metrics |
cvssV3_1
|
Mon, 09 Mar 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 09 Mar 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Parse Community
Parse Community parse Server |
|
| Vendors & Products |
Parse Community
Parse Community parse Server |
Sat, 07 Mar 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Parse Server: JWT audience validation bypass in Google, Apple, and Facebook authentication adapters | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-09T18:25:24.090Z
Reserved: 2026-03-05T21:27:35.342Z
Link: CVE-2026-30863
Updated: 2026-03-09T16:43:53.833Z
Status : Analyzed
Published: 2026-03-07T17:15:54.137
Modified: 2026-03-10T16:50:58.427
Link: CVE-2026-30863
No data.
OpenCVE Enrichment
Updated: 2026-04-18T10:00:10Z
Github GHSA