{{ message }}
Security: parse-community/parse-server
Security
SECURITY.md
If you believe you have found a security vulnerability on one of parse-community maintained packages, we encourage you to let us know right away. We will investigate all legitimate reports and do our best to quickly fix the problem. Before making a report, please review this page to understand our disclosure policy and how to communicate with us.
If you comply with the policies below when reporting a security issue to parse community, we will not initiate a lawsuit or law enforcement investigation against you in response to your report. We ask that:
- You give us reasonable time to investigate and mitigate an issue you report before making public any information about the report or sharing such information with others. This means we request at least 7 days to get back to you with an initial response and at least 30 days from initial contact (made by you) to apply a patch.
- You do not interact with an individual account (which includes modifying or accessing data from the account) if the account owner has not consented to such actions.
- You make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) destruction of data and interruption or degradation of our services.
- You do not exploit a security issue you discover for any reason. (This includes demonstrating additional risk, such as attempted compromise of sensitive company data or probing for additional issues). You do not violate any other applicable laws or regulations.
All vulnerabilities should be privately reported to us by going to https://report.parseplatform.org. Alternatively, you can send an email to security@parseplatform.org.
-
LiveQuery discloses object data to a subscriber across an ACL read-access changeGHSA-97pr-9hgg-3p8r published
Jun 19, 2026 by mtrezzaLow -
Denial of service via exponential-time processing of deeply nested query operatorsGHSA-cgxm-vr2f-6fj8 published
Jun 17, 2026 by mtrezzaHigh -
Stored XSS via non-standard file extension bypassing file upload extension blocklistGHSA-v8x7-r927-cc93 published
Jun 16, 2026 by mtrezzaLow -
Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is deniedGHSA-75v4-m273-5j49 published
Jun 3, 2026 by mtrezzaModerate -
Stored XSS via trailing-dot filename bypassing file upload extension blocklistGHSA-7wqv-xjf3-x35v published
Jun 1, 2026 by mtrezzaLow -
Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACLGHSA-wmwx-jr2p-4j4r published
Jun 4, 2026 by mtrezzaModerate -
Server option routeAllowList is bypassable through batch sub-requestsGHSA-p84r-h6rx-f2xr published
May 27, 2026 by mtrezzaModerate -
Pre-authentication denial of service via client version header regex backtrackingGHSA-38m6-82c8-4xfm published
May 17, 2026 by mtrezzaHigh -
GraphQL "Did you mean" validation suggestions disclose schema to unauthenticated callersGHSA-8cph-rgr4-g5vj published
May 18, 2026 by mtrezzaModerate -
MFA SMS one-time password accepted twice under concurrent loginGHSA-jpq4-7fmq-q5fj published
Apr 26, 2026 by mtrezzaLow
Learn more about advisories related to parse-community/parse-server in the GitHub Advisory Database