Live › vulnerability › CVE-2026-112769
Go to dashboardParse Server does not enforce the create and addField class-level permissions on the _Session class when sessions are created. An authenticated user, or anyone holding that user's session token, can create extra sessions for that user and add fields to _Session, and those sessions stay valid after the original session is logged out.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications running Parse Server before 8.6.98 or 9.0.0 through 9.10.2 that let users authenticate. The flaw matters when a user or a leaked session token can reach the session endpoints. Deployments that do not expose Parse Server to authenticated users, or that run a patched version, can skip it.
No product ranges from the sources yet.
npm ls parse-server and compare it with 8.6.98 (8.x line) or 9.10.3-alpha.1 (9.x line)._Session in your app to see whether create or addField is restricted.8.6.98 on the 8.x line, or to 9.10.3-alpha.1 or later on the 9.x line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Parse Server before 8.6.98 and 9.0.0 before 9.10.3-alpha.1 does not enforce the create and addField class-level permissions of the _Session class when creating sessions. An authenticated user, or anyone holding that user's session token, can send POST requests to /sessions or /classes/_Session to create additional sessions for that user and add fields to _Session; these sessions are not revoked when the original session is logged out.
This page as .md · .json · in your agent: get_signal("CVE-2026-112769")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.