Affects Azure AD OAuth flow; widely used in enterprise IdP integrations; could enable token theft and session hijack across many organizations.
CVE-2026-56425
Azure AD OAuth flow flaws enable session hijack, fixation, and token leakage.
Is CVE-2026-56425 being exploited?
Not confirmed. CVE-2026-56425 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-56425?
CVE-2026-56425 is rated Critical with a CVSS score of 9.3. 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-56425?
Yes. A fix has been recorded for CVE-2026-56425. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56425 affect?
CVE-2026-56425 affects Azure Active Directory, AAD OAuth 2.0 integration, Azure AD authentication plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56425?
Apply patch; enforce HTTPS; rotate sessions; review logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers could hijack sessions via leaked OAuth state and session_id; CSRF risk; token exposure on non-HTTPS redirects.
Patch when possible
- affected<= 2.5.41
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.