Quick answers
- Is CVE-2026-101042 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101042 being exploited in the wild.
- How severe is CVE-2026-101042?
- Medium severity, with a CVSS score of 6.4, published 27 September 2026.
- Which products and versions are affected?
- Parse Community Parse Server >=9.0.0 <9.10.1-alpha.10 and >=8.0.2 <8.6.91.
- Is there a fix for CVE-2026-101042?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-101042 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-101042?
- Check whether you run Parse Community Parse Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in Parse Server's code-based authentication adapters, which verify provider credentials during signup and account linking but skip verification during login when auth data is combined with username/password. An authenticated attacker can exploit this by submitting an unverified provider identity on the login endpoint; a network attacker can pre-hijack accounts by claiming provider IDs of future users. The fix involves running credential verification on login/challenge endpoints and preventing duplicate provider identity linkage across accounts.
Affected products
- Parse Community Parse Server >=9.0.0 <9.10.1-alpha.10 and >=8.0.2 <8.6.91
Timeline
- 2026-09-27: disclosed: Security advisory published