CVE-2026-34574
Parseplatform Parse-Server ≤ 8.6.69
Raw vector
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:XSummary
CVE-2026-34574 is a medium-severity Incorrect Comparison (CWE-697) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-17502
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Bypassing session expiry on authenticated accounts directly enables indefinite use of valid sessions/accounts for persistence.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces immutability rules on session objects so that authenticated users cannot overwrite expiresAt/createdWith via PUT.
Rejects or sanitizes the null values supplied for protected session fields before the update logic is reached.
Limits the set of session attributes an ordinary user is permitted to modify, reducing the impact of any bypass of the immutability guard.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly require correct logic for security comparisons and thereby prevent this class of flaw.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect incorrect comparison flaws before deployment.
Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.
Application security requirements can mandate correct comparison logic for security decisions.
Secure architecture principles can require robust comparison mechanisms for access decisions.
Secure coding standards directly address avoiding incorrect comparison operators and logic.
Secure authentication mechanisms rely on correct comparison of credentials or tokens.