The readOnlyMasterKey can call POST /loginAs to obtain a valid session token for any user. This allows a read-only credential to impersonate arbitrary users with full read and write access to their data. Any Parse Server deployment that uses readOnlyMasterKey is affected.
The fix adds a check to the /logInAs handler.
There is no workaround other than not using readOnlyMasterKey.
{
"severity": "HIGH",
"cwe_ids": [
"CWE-863"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-06T18:46:27Z",
"nvd_published_at": "2026-03-06T21:16:16Z"
}