CVE-2026-56425

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)

• CWE-384

• https://github.com/MISP/MISP/commit/146bc40ad6e10a44f01e8ed62d5f7bc9c06cc4faPatch

Published

Jun 22, 2026

Last Modified

Jun 26, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-56415Storage Concentrator (SC & SCVM) contains a command injectio…10
• CVE-2026-56416In NLnet Labs Unbound up to and including version 1.25.1, wh…4.8
• CVE-2026-5642A vulnerability was determined in Cyber-III Student-Manageme…7.3
• CVE-2026-56422Multiple MISP core controllers and model capture paths accep…9.4
• CVE-2026-56423MISP Core contained broken access-control checks in the bulk…8.8
• CVE-2026-56424MISP core contained multiple broken access-control flaws whe…8.8
• CVE-2026-56428The SSH service on BSH ELP (Electronic Platform) modules con…8.1
• CVE-2026-5643A vulnerability was identified in Cyber-III Student-Manageme…2.4
• CVE-2026-56434NGINX Plus and NGINX Open Source have a vulnerability in the…8.3
• CVE-2026-56437Uncontrolled search path element issue exists in Pupsman ver…8.4
• CVE-2026-5644A security flaw has been discovered in Cyber-III Student-Man…2.4
• CVE-2026-56444In NLnet Labs Unbound 1.20.0 up to and including 1.25.1, whe…5.9