Parse Platform parse-server 9.3.1 Alpha 3 for Node.js
Approved changes feed: RSS · Atom
cpe:2.3:a:parseplatform:parse-server:9.3.1:alpha3:*:*:*:node.js:*:*
part: a version: 9.3.1 update: alpha3
| Vendor | Parseplatform (6383af77-895d-54d6-99f0-fd04347d92e2) |
|---|---|
| Product | Parse Server (63c30d4d-66ac-5ebe-9ef3-82524e7c616b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/parsecommunity/parseserver |
purl2cpe | 2026-06-01 10:16:40.301620 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-30854 |
vulnerable | 2026-06-08 07:57:14.381997 |
Parse Server: GraphQL `__type` introspection bypass via inline fragments when public introspection is disabled
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version 9.3.1-alpha.3 to before version 9.5.0-alpha.10, when graphQLPublicIntrospection is disabled, __type queries nested inside inline fragments (e.g. ... on Query { __type(name:"User") { name } }) bypass the introspection control, allowing unauthenticated users to perform type reconnaissance. __schema introspection is not affected. This issue has been patched in version 9.5.0-alpha.10.
Published: 2026-03-07T16:24:10.312Z
Updated: 2026-03-09T18:25:03.815Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27804 |
vulnerable | 2026-06-08 07:55:13.915952 |
Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.3 and 9.1.1-alpha.4, an unauthenticated attacker can forge a Google authentication token with `alg: "none"` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. The fix in versions 8.6.3 and 9.1.1-alpha.4 hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter's custom key fetcher with `jwks-rsa` which rejects unknown key IDs. As a workaround, dsable Google authentication until upgrading is possible.
Published: 2026-02-25T23:48:20.858Z
Updated: 2026-02-26T17:03:50.903Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.