CVE-2026-55987
OAuth2 sign-in can reactivate admin-disabled accounts, enabling account takeover.
Is CVE-2026-55987 being exploited?
Not confirmed. CVE-2026-55987 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-55987?
CVE-2026-55987 is rated High with a CVSS score of 8.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-55987?
Yes. A fix has been recorded for CVE-2026-55987. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55987 affect?
CVE-2026-55987 affects OAuth2-based SSO integrations, Identity providers (IdP), Applications using OAuth2 sign-on, Auth sources without refresh tokens. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55987?
Disable OAuth2 sign-in for disabled accounts, audit affected accounts, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
OAuth2 sign-in reactivates admin-deactivated accounts (no refresh token), enabling account takeover and potential admin privilege escalation.
Immediate action required
- affected<= 1.26.4
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.