A flaw was found in the SAML protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs when Keycloak handles SAML authentication requests using the HTTP-Redirect binding. If a client is configured with a wildcard redirect URL, an attacker can craft a request that includes malicious parameters. When a user authenticates, Keycloak appends its legitimate response to the attacker's parameters. This can cause some service providers to process the attacker's data instead of the real login information, potentially leading to a user being logged into the wrong account.
CVE-2026-18217
This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(medium)
- EG Risk
- 21(Track)EG Risk 21/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 computedSeverity47% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
August 7, 2026
Advisory Details (2)
Auto-updated Aug 7, 20262508311 – (CVE-2026-18217) CVE-2026-18217 keycloak-services: keycloak-services: SAML HTTP-Redirect binding response preserves query string leading to parameter pollution
https://bugzilla.redhat.com/show_bug.cgi?id=2508311CVE-2026-18217 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-18217Vendor Advisories for CVE-2026-18217(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 21× in last 7d / 57× 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.
- 2026-08-20 23:37 UTCEG score recompute
- 2026-08-20 23:37 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 23:13 UTCEG score recompute
- 2026-08-19 23:13 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 22:48 UTCEG score recompute
- 2026-08-18 22:48 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 22:14 UTCEG score recompute
- 2026-08-17 22:14 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 21:49 UTCEG score recompute
- 2026-08-16 21:49 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 21:24 UTCEG score recompute
- 2026-08-15 21:24 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 20:59 UTCEG score recompute
- 2026-08-14 20:59 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 20:34 UTCGHSA enrichment
- 2026-08-12 20:09 UTCEG score recompute
- 2026-08-12 20:09 UTCGHSA enrichment
Show 32 moreShow fewer
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 19:44 UTCEG score recompute
- 2026-08-11 19:44 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 19:20 UTCGHSA enrichment
- 2026-08-09 18:55 UTCEG score recompute
- 2026-08-09 18:55 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 18:31 UTCEG score recompute
- 2026-08-08 18:31 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 18:06 UTCEG score recompute▲ 1.30
- 2026-08-07 18:06 UTCGHSA enrichment
- 2026-08-07 18:05 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
- 2026-08-06 17:44 UTCEG score recompute
- 2026-08-06 17:44 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 16:56 UTCEG score recompute
- 2026-08-03 16:56 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 20:23 UTCEG score recompute
- 2026-07-31 20:23 UTCGHSA enrichment
- 2026-07-31 19:48 UTCEG score recompute
- 2026-07-31 19:48 UTCGHSA enrichment
- 2026-07-31 08:18 UTCEG score recompute
- 2026-07-31 07:28 UTCEG score recompute
- 2026-07-31 07:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-18217?
When was CVE-2026-18217 disclosed?
Is CVE-2026-18217 actively exploited?
What is the CVSS score of CVE-2026-18217?
How do I remediate CVE-2026-18217?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18217
Is Your Infrastructure Affected by CVE-2026-18217?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.