CVE-2026-32242
OAuth2 token validation across providers may bypass per-provider policies.
Is CVE-2026-32242 being exploited?
Not confirmed. CVE-2026-32242 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-32242?
CVE-2026-32242 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32242?
Yes. A fix has been recorded for CVE-2026-32242. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32242 affect?
CVE-2026-32242 affects Parse Server deployments with multiple OAuth2 providers (oauth2: true). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32242?
Patch to 9.6.0-alpha.11 or 8.6.37+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authentication bypass: token from one OAuth2 provider may be accepted due to shared config, enabling impersonation.
Immediate action required
- affected>= 9.0.0 and < 9.6.0-alpha.11
- affected< 8.6.37
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.