Advisory

GHSA-6r2j-cxgf-495f

Also known as: BIT-parse-2026-30965, CVE-2026-30965

Summary

Parse Server vulnerable to session token exfiltration via redirectClassNameForKey query parameter

Details

Impact

A vulnerability in Parse Server's query handling allows an authenticated or unauthenticated attacker to exfiltrate session tokens of other users by exploiting the redirectClassNameForKey query parameter. Exfiltrated session tokens can be used to take over user accounts.

The vulnerability requires the attacker to be able to create or update an object with a new relation field, which depends on the Class-Level Permissions of at least one class.

Patches

The fix applies the same security checks that normally protect class access after the query redirect, ensuring that queries redirected via redirectClassNameForKey are subject to the same restrictions as direct queries to the target class.

Workarounds

Set restrictive Class-Level Permissions to prevent clients from creating new fields on classes, specifically by disabling addField for public access and unauthenticated users. Note that this limits client functionality and does not fully eliminate the risk if a relation field pointing to a protected class already exists in the schema.

References

  • GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-6r2j-cxgf-495f
  • Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.8
  • Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.21

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-03-11 00:20 UTC
Modified
2026-03-14 03:41 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0-alpha.1, fixed 9.5.2-alpha.8 (semver)

Fixed versions

9.5.2-alpha.8

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.21 (semver)

Fixed versions

8.6.21

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences