CVE-2026-34574 [Medium] | Security Bypass in Parse-Server

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.69 and 9.7.0-alpha.14, an authenticated user can bypass the immutability guard on session fields (expiresAt, createdWith) by sending a null value in a PUT request to the session update endpoint. This allows nullifying the session expiry, making the session valid indefinitely and bypassing configured session length policies. This issue has been patched in versions 8.6.69 and 9.7.0-alpha.14.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-01	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-01

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.3	4.0	MEDIUM	`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network. Attack complexity (AC:L) Exploitation conditions are straightforward and stable. Attack requirements (AT:N) No additional preconditions are required beyond normal reachability. Privileges required (PR:L) Low privileges are required. User interaction (UI:N) No user interaction is required. Vulnerable system confidentiality impact (VC:L) Limited confidentiality impact on the vulnerable system. Vulnerable system integrity impact (VI:L) Limited integrity impact on the vulnerable system. Vulnerable system availability impact (VA:N) No availability impact on the vulnerable system. Subsequent system confidentiality impact (SC:N) No confidentiality impact on subsequent systems. Subsequent system integrity impact (SI:N) No integrity impact on subsequent systems. Subsequent system availability impact (SA:N) No availability impact on subsequent systems. Exploit maturity (threat) (E:X) Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked). Confidentiality requirement (CR:X) Not defined: insufficient information; scoring treats this like High (worst case). Integrity requirement (IR:X) Not defined: insufficient information; scoring treats this like High (worst case). Availability requirement (AR:X) Not defined: insufficient information; scoring treats this like High (worst case). Modified attack vector (MAV:X) Not defined: scoring uses the Base Attack Vector (AV). Modified attack complexity (MAC:X) Not defined: scoring uses the Base Attack Complexity (AC). Modified attack requirements (MAT:X) Not defined: scoring uses the Base Attack Requirements (AT). Modified privileges required (MPR:X) Not defined: scoring uses the Base Privileges Required (PR). Modified user interaction (MUI:X) Not defined: scoring uses the Base User Interaction (UI). Modified vulnerable system confidentiality impact (MVC:X) Not defined: scoring uses the Base VC metric. Modified vulnerable system integrity impact (MVI:X) Not defined: scoring uses the Base VI metric. Modified vulnerable system availability impact (MVA:X) Not defined: scoring uses the Base VA metric. Modified subsequent system confidentiality impact (MSC:X) Not defined: scoring uses the Base SC metric. Modified subsequent system integrity impact (MSI:X) Not defined: scoring uses the Base SI metric. Modified subsequent system availability impact (MSA:X) Not defined: scoring uses the Base SA metric. Safety (supplemental) (S:X) Not evaluated. Automatable (supplemental) (AU:X) Not evaluated. Recovery (supplemental) (R:X) Not evaluated. Value density (supplemental) (V:X) Not evaluated. Vulnerability response effort (supplemental) (RE:X) Not evaluated. Provider urgency (supplemental) (U:X) Not evaluated.	—	—	[email protected]
5.4	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	2.5	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.3

4.0

MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L): Exploitation conditions are straightforward and stable.
Attack requirements (AT:N): No additional preconditions are required beyond normal reachability.
Privileges required (PR:L): Low privileges are required.
User interaction (UI:N): No user interaction is required.
Vulnerable system confidentiality impact (VC:L): Limited confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:L): Limited integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:N): No availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N): No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N): No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N): No availability impact on subsequent systems.
Exploit maturity (threat) (E:X): Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X): Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X): Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X): Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X): Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X): Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X): Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X): Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X): Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X): Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X): Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X): Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X): Not evaluated.
Automatable (supplemental) (AU:X): Not evaluated.
Recovery (supplemental) (R:X): Not evaluated.
Value density (supplemental) (V:X): Not evaluated.
Vulnerability response effort (supplemental) (RE:X): Not evaluated.
Provider urgency (supplemental) (U:X): Not evaluated.

—

[email protected]

5.4

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

2.5

[email protected]

Affected software / configurations for CVE-2026-34574

Vendor	Product	Version	Raw CPE
parseplatform	parse-server	< 8.6.69	cpe:2.3:a:parseplatform:parse-server::::::node.js::*
parseplatform	parse-server	>= 9.0.0, < 9.7.0	cpe:2.3:a:parseplatform:parse-server::::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha1::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha10::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha11::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha12::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha13::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha2::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha3::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha4::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha5::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha6::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha7::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha8::::node.js::*
parseplatform	parse-server	9.7.0	cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha9::::node.js::*

References for CVE-2026-34574

URL	Tags
https://github.com/parse-community/parse-server/commit/90802969fc713b7bc9733d7255c7519a6ed75d21	Patch
https://github.com/parse-community/parse-server/commit/ebccd7fe2708007e62f705ee1c820a6766178777	Patch
https://github.com/parse-community/parse-server/pull/10347	Issue Tracking Patch
https://github.com/parse-community/parse-server/pull/10348	Issue Tracking Patch
https://github.com/parse-community/parse-server/security/advisories/GHSA-f6j3-w9v3-cq22	Patch Vendor Advisory

URL

CVE-2026-34574 | Parse Server: Session field immutability bypass via falsy-value guard

Exploit prediction scoring system (EPSS) score for CVE-2026-34574

Common vulnerability scoring system (CVSS) metrics for CVE-2026-34574

Weakness enumeration for CVE-2026-34574

GitHub Security Advisory for CVE-2026-34574

Affected software / configurations for CVE-2026-34574

References for CVE-2026-34574