CVE-2026-7507

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-19. a secondary CVSS source baseline 7.5; sources differ by 0.0.

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

A fix is available — apply it.

A session fixation vulnerability was found in Keycloak's login-actions endpoints. An unauthenticated attacker could exploit this flaw by pre-creating an authentication session and tricking a victim into visiting a maliciously crafted link. By leveraging the /login-actions/restart endpoint—which processes session handles without adequate CSRF protection or cookie ownership validation—an attacker can reset the authentication flow state. This causes Single Sign-On (SSO) to authenticate the victim transparently upon clicking the link, allowing the attacker to hijack the required-action form without needing the victim's credentials. A successful exploit could lead to complete account takeover, including highly privileged administrative accounts.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jun 11, 2026
Patch available. Sources: redhat.
redhat

2464145 – (CVE-2026-7507) CVE-2026-7507 org.keycloak/keycloak-services: Session fixation in OIDC login flow that can lead to account takeover

https://bugzilla.redhat.com/show_bug.cgi?id=2464145
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-7507
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19597
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19596
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19595
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19594

Vendor Advisories for CVE-2026-7507(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.2-212026-05-20redhat
redhatrhbk/keycloak-rhel9-operator2026-05-20redhat
redhatrhbk/keycloak-rhel9-operator:26.4-172026-05-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (226 versions)26.6.2—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 72× 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 204 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-7507?
CVE-2026-7507 is a high vulnerability published on May 19, 2026. A session fixation vulnerability was found in Keycloak's login-actions endpoints. An unauthenticated attacker could exploit this flaw by pre-creating an authentication session and tricking a victim into visiting a maliciously crafted link. By leveraging the /login-actions/restart endpoint—which…
When was CVE-2026-7507 disclosed?
CVE-2026-7507 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7507 actively exploited?
CVE-2026-7507 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.5% of all scored CVEs.
What is the CVSS score of CVE-2026-7507?
CVE-2026-7507 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-7507?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7507, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7507

Explore →

Is Your Infrastructure Affected by CVE-2026-7507?

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

Start Free Scan →Browse All CVEs