CVE-2026-56425

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-22. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit 146bc40ad6e1 (MISP/MISP)

Patch available: MISP/MISP v2.5.42 (contains commit 146bc40ad6e1)

https://github.com/MISP/MISP/commit/146bc40ad6e10a44f01e8ed62d5f7bc9c06cc4fa

Vendor Advisories for CVE-2026-56425(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-07-27 21:16 UTCEG score recompute
  2. 2026-07-27 21:16 UTCGHSA enrichment
  3. 2026-07-27 06:29 UTCGHSA enrichment
  4. 2026-07-26 16:05 UTCEG score recompute
  5. 2026-07-26 16:04 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:20 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 18:58 UTCGHSA enrichment
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-16 04:21 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 15:17 UTCGHSA enrichment
  24. 2026-07-15 02:13 UTCGHSA enrichment
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 13:02 UTCGHSA enrichment
  3. 2026-07-13 23:58 UTCGHSA enrichment
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 10:54 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 21:51 UTCGHSA enrichment
  9. 2026-07-12 08:47 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 19:41 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 06:36 UTCGHSA enrichment
  15. 2026-07-10 17:32 UTCGHSA enrichment
  16. 2026-07-10 04:26 UTCGHSA enrichment
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 15:16 UTCGHSA enrichment
  20. 2026-07-09 01:18 UTCGHSA enrichment
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 12:14 UTCGHSA enrichment
  24. 2026-07-07 22:39 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-07 13:46 UTCEPSS rescore
  27. 2026-07-07 09:35 UTCGHSA enrichment
  28. 2026-07-06 20:29 UTCGHSA enrichment
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 16:27 UTCEPSS rescore
  31. 2026-07-06 06:43 UTCGHSA enrichment
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-06 02:23 UTCEPSS rescore
  34. 2026-07-05 17:38 UTCGHSA enrichment
  35. 2026-07-05 04:34 UTCGHSA enrichment
  36. 2026-07-05 02:31 UTCEPSS rescore
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-04 15:30 UTCGHSA enrichment
  39. 2026-07-04 06:31 UTCEPSS rescore
  40. 2026-07-04 06:31 UTCEPSS rescore
  41. 2026-07-04 02:25 UTCGHSA enrichment
  42. 2026-07-03 13:14 UTCGHSA enrichment
  43. 2026-07-03 00:09 UTCGHSA enrichment
  44. 2026-07-02 11:06 UTCGHSA enrichment
  45. 2026-07-01 21:27 UTCGHSA enrichment
  46. 2026-07-01 15:07 UTCEPSS rescore
  47. 2026-07-01 08:23 UTCGHSA enrichment
  48. 2026-06-30 23:22 UTCEPSS rescore
  49. 2026-06-30 19:19 UTCGHSA enrichment
  50. 2026-06-30 06:15 UTCGHSA enrichment
  51. 2026-06-29 17:11 UTCGHSA enrichment
  52. 2026-06-29 14:06 UTCEPSS rescore
  53. 2026-06-29 04:01 UTCGHSA enrichment
  54. 2026-06-28 14:53 UTCGHSA enrichment
  55. 2026-06-28 14:07 UTCEPSS rescore
  56. 2026-06-28 04:56 UTCEPSS rescore
  57. 2026-06-28 04:56 UTCEPSS rescore
  58. 2026-06-28 01:49 UTCGHSA enrichment
  59. 2026-06-27 12:45 UTCGHSA enrichment
  60. 2026-06-27 03:08 UTCEPSS rescore
  61. 2026-06-26 23:41 UTCEG score recompute 0.50
  62. 2026-06-26 23:41 UTCGHSA enrichment
  63. 2026-06-26 21:42 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  64. 2026-06-26 19:30 UTCGHSA enrichment
  65. 2026-06-26 15:19 UTCGHSA enrichment
  66. 2026-06-26 11:08 UTCGHSA enrichment
  67. 2026-06-26 04:52 UTCGHSA enrichment
  68. 2026-06-26 00:40 UTCGHSA enrichment
  69. 2026-06-25 20:29 UTCGHSA enrichment
  70. 2026-06-25 16:18 UTCGHSA enrichment
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-25 12:06 UTCGHSA enrichment
  73. 2026-06-25 07:55 UTCGHSA enrichment
  74. 2026-06-25 03:43 UTCGHSA enrichment
  75. 2026-06-24 23:32 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56425?
CVE-2026-56425 is a high vulnerability published on June 22, 2026. 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…
When was CVE-2026-56425 disclosed?
CVE-2026-56425 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56425 actively exploited?
CVE-2026-56425 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.6% of all scored CVEs.
What is the CVSS score of CVE-2026-56425?
CVE-2026-56425 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56425?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56425, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56425

Explore →

Is Your Infrastructure Affected by CVE-2026-56425?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.