VulnerabilityPublished 6 Mar 2026Updated 9 Mar 2026

CVE-2026-30229: parse-server · Incorrect Authorization

Affects parse-serverSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 9.5.0-alpha.4 or 8.6.6 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

8.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.5.0-alpha.4, 8.6.6

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade parse-server to 9.5.0-alpha.4 or 8.6.6; parse-community/parse-server to 8.6.6.

Affected software

Product	Affected	Fixed in
parse-communityparse-server	Affected <9.5.0-alpha.4	Fixed in 9.5.0-alpha.4
parse-communityparse-server	Affected <8.6.6	Fixed in 8.6.6
npmparse-community/parse-server`pkg:npm/parse-community/parse-server`Other threats	Affected <8.6.6 =9.5.0-alpha.4	Fixed in 8.6.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately upgrade all parse-server deployments to version 8.6.6 or later (including 9.5.0-alpha.4 and beyond) to apply the official patch addressing this vulnerability.
Audit and rotate all readOnlyMasterKey credentials to prevent unauthorized use of compromised keys.
Restrict access to the readOnlyMasterKey to trusted systems and personnel only, employing strict access controls and monitoring.
Implement network-level controls such as IP whitelisting and firewall rules to limit access to parse-server administrative endpoints.
Enable detailed logging and monitoring of all authentication and session token generation activities, especially calls to POST /loginAs, to detect anomalous usage.
Conduct a thorough review of application and backend logs to identify any suspicious activity or potential exploitation prior to patching.
Educate development and operations teams about the risks of improper key management and the importance of timely patching.
Consider implementing additional application-layer authorization checks or multi-factor authentication for sensitive operations if feasible.
Regularly review and update security policies related to key management and backend access controls to prevent similar issues.

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.6 and 9.5.0-alpha.4, 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. This issue has been patched in versions 8.6.6 and 9.5.0-alpha.4.

Impact

The vulnerability allows an attacker with access to the readOnlyMasterKey to impersonate any user and gain full read and write access to their data. This can lead to unauthorized data disclosure, data modification, and potential data destruction. Organizations relying on parse-server for backend services risk severe breaches of user privacy and data integrity. Attackers could manipulate user data, escalate privileges, or perform fraudulent actions on behalf of users. Since the readOnlyMasterKey is often used in integrations or monitoring, its compromise could go unnoticed, enabling persistent unauthorized access. The impact extends to any application built on parse-server, including mobile apps, web services, and IoT backends, potentially affecting millions of users. The vulnerability undermines trust in the security of affected applications and could lead to regulatory penalties if sensitive data is exposed. The lack of known exploits in the wild currently reduces immediate risk but does not diminish the urgency of remediation.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Mar 2026, 19:45 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats