CVE & CISA-KEV Catalog

CVE-2026-56425

HIGH
8.8
CVSS v3
NVD

Description

The Azure Active Directory (AAD) authentication implementation contained multiple weaknesses in its OAuth 2.0 authorization flow that could allow attackers to bypass important security guarantees provided by the protocol. The application used the PHP session identifier (session_id()) as the OAuth state parameter. Because session identifiers are long-lived authentication credentials, exposing them in OAuth redirect URLs could leak valid session tokens through browser history, HTTP Referer headers, reverse proxies, access logs, or third-party infrastructure involved in the authentication flow. If obtained by an attacker, the leaked session identifier could potentially be used for session hijacking. Additionally, the implementation did not regenerate the session identifier after successful authentication, leaving authenticated sessions susceptible to session fixation attacks where an attacker forces a victim to use a known session identifier before login and later reuses that identifier after authentication. The OAuth state value was also not implemented as a dedicated, single-use nonce. This weakened CSRF protections and increased the risk of replay attacks against the OAuth callback process. The authentication flow further failed to enforce HTTPS for the configured OAuth redirect URI. If a non-HTTPS redirect URI was used, OAuth authorization codes and access tokens could traverse the network in plaintext, exposing sensitive credentials to network attackers. Finally, OAuth error responses containing attacker-controlled GET parameters were logged verbatim. An attacker could inject control characters or crafted log content, leading to log forging, log injection, or corruption of audit records. The fix introduces: * A dedicated cryptographically random OAuth state value. * Single-use state validation and invalidation. * Constant-time state comparison using hash_equals(). * Session identifier rotation after successful authentication. * Enforcement of HTTPS-only redirect URIs. * Sanitized and length-limited logging of OAuth error parameters. AAD Authentication Plugin (OAuth 2.0 / Azure Active Directory integration)

How to fix

Remediation Available
mispNVD
Affected:< 2.5.42Fixed in:2.5.42CVE-2026-56425derived from NVD

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploit Intelligence

0.46%probability of exploitation in 30 days
38thpercentile

Low risk: more likely to be exploited than 38% of all known CVEs.

References

Related Vulnerabilities

Other CWE-384 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2018-11714Critical9.832%--
CVE-2019-12258High7.523%-Fix
CVE-2019-10008High8.822%--
CVE-2018-17199High7.521%-Fix
CVE-2024-50339Medium5.320%-Fix
CVE-2018-18925Critical9.818%--

Common questions

How do I fix CVE-2026-56425?

Upgrade misp to 2.5.42 or later.

Is CVE-2026-56425 being actively exploited?

Not that we know of. CVE-2026-56425 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.46% is the estimated probability that it will be exploited in the next 30 days. That is higher than 38% of all scored CVEs.

How severe is CVE-2026-56425?

CVE-2026-56425 has a CVSS v3 base score of 8.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-56425 affect?

Published advisories record a fix for misp (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-56425
CVE-2026-56425 severity badge

Markdown

[![CVE-2026-56425](https://tridentstack.com/cve/badge/CVE-2026-56425.svg)](https://tridentstack.com/cve/CVE-2026-56425)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-56425"><img src="https://tridentstack.com/cve/badge/CVE-2026-56425.svg" alt="CVE-2026-56425"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-26.