CVE-2026-18206

LOWNVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-31. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

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

A flaw was found in the keycloak-services component of Keycloak, which provides identity and access management services. The issue occurs when a realm administrator uses a wildcard domain (like *.example.com) to restrict which hosts can register or update clients. Due to improper validation, the system accepts any hostname that ends with the specified domain suffix, even if it is not a legitimate subdomain. An attacker who can control the reverse DNS of their connection can bypass these host-based restrictions, potentially allowing unauthorized client modifications.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
17(Track)
EG Risk 17/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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 7, 2026

References (2)

Vendor Advisories for CVE-2026-18206(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 11× in last 7d / 42× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 19:26 UTCEG score recompute
  3. 2026-08-19 19:26 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 17:19 UTCEG score recompute
  8. 2026-08-16 17:19 UTCGHSA enrichment
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 16:41 UTCEG score recompute
  14. 2026-08-13 16:41 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 15:55 UTCEG score recompute
  19. 2026-08-10 15:55 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 15:07 UTCEG score recompute
  23. 2026-08-07 15:07 UTCGHSA enrichment
  24. 2026-08-06 17:33 UTCEG score recompute
  25. 2026-08-06 17:33 UTCGHSA enrichment
Show 17 more
  1. 2026-08-06 13:46 UTCEPSS rescore
  2. 2026-08-05 19:17 UTCEPSS rescore
  3. 2026-08-04 15:10 UTCEPSS rescore
  4. 2026-08-04 10:38 UTCEPSS rescore
  5. 2026-08-03 16:56 UTCGHSA enrichment
  6. 2026-08-03 12:04 UTCEG score recompute
  7. 2026-08-03 12:04 UTCGHSA enrichment
  8. 2026-08-03 10:35 UTCEPSS rescore
  9. 2026-08-02 02:26 UTCEPSS rescore
  10. 2026-08-01 04:15 UTCEPSS rescore
  11. 2026-07-31 11:26 UTCEG score recompute
  12. 2026-07-31 11:26 UTCGHSA enrichment
  13. 2026-07-31 11:15 UTCEG score recompute
  14. 2026-07-31 11:15 UTCGHSA enrichment
  15. 2026-07-31 08:18 UTCEG score recompute
  16. 2026-07-31 07:28 UTCEG score recompute
  17. 2026-07-31 07:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18206?
CVE-2026-18206 is a low vulnerability published on July 31, 2026. A flaw was found in the keycloak-services component of Keycloak, which provides identity and access management services. The issue occurs when a realm administrator uses a wildcard domain (like *.example.com) to restrict which hosts can register or update clients. Due to improper validation, the…
When was CVE-2026-18206 disclosed?
CVE-2026-18206 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18206 actively exploited?
CVE-2026-18206 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 89.7% of all scored CVEs.
What is the CVSS score of CVE-2026-18206?
CVE-2026-18206 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-18206?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18206, 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-18206

Explore →

Is Your Infrastructure Affected by CVE-2026-18206?

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

Start Free Scan →Browse All CVEs