Parse Server
Open-source backend platform for mobile and web apps
Parse Server's 9.10.1 alpha series has patched five separate GHSA security advisories in three weeks — auth, data, and field exposure all affected.
◆Recent moves
- 1d ago
Rate limit bypass via X-Forwarded-For header fixed
Rate limit enforcement could be bypassed by setting X-Forwarded-For: 127.0.0.1 on servers with a permissive trustProxy configuration. The fifth security fix in this alpha series, reinforcing the pattern of systematic security hardening underway in 9.10.1.
View source ↗ - 2d ago
Unverified auth provider identity accepted on password login (GHSA)
A code-based auth adapter flaw allowed an unverified auth provider identity to pass on a password login, creating an authentication gap. Part of the GHSA series that defines this alpha cycle.
View source ↗ - 6d ago
Unauthenticated deletion via operator injection in device tokens
⚡ SPARKAn unauthenticated attacker could delete installation records by injecting operators into the device token deduplication path — no credentials required. This is the most exploitable class of vulnerability in this cycle and represents the kind of issue that forces immediate action from self-hosters.
View source ↗ - 6d ago
LiveQuery leaks protected fields to partially identified subscribers
LiveQuery subscribers with incomplete identity resolution could receive protected field values they should not see. An information disclosure bug that compounds the trust concerns from this alpha cycle's broader security review.
View source ↗ - 20d ago
Account takeover via empty password in LDAP auth adapter
⚡ SPARKThe LDAP auth adapter accepted an empty string as a valid password, enabling account takeover on any user with LDAP authentication enabled. A complete authentication bypass — the most trust-damaging vulnerability in this series.
View source ↗ - 1mo ago
Parse.Query.explain incorrectly triggers afterFind hooks on query plans
Parse.Query.explain was incorrectly running afterFind triggers on query plan results rather than actual query output, causing unexpected side effects for developers using explain for query analysis. A correctness bug with no security implications.
View source ↗