HCL iControl is affected by Weak SSL/TLS Version Supported vulnerability. It was observed that the application was using weak TLS versions such as TLS 1.0 and 1.1. These outdated protocols lack modern security features, making them vulnerable to known attacks and exposing sensitive information during data transmission.
CVE-2026-56609
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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
- 6.5
- EG Score
- 6.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 computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 3, 2026
Last Modified
August 5, 2026
Advisory Details (1)
Auto-updated Aug 3, 2026Security Bulletin: Multiple security vulnerabilities affect HCL iControl (CVE-2026-56608 and CVE-2026-56609) - Customer Support
https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0132564Vendor Advisories for CVE-2026-56609(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 17× in last 7d / 48× 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 22:55 UTCEPSS rescore
- 2026-08-20 12:20 UTCEG score recompute
- 2026-08-20 12:20 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:49 UTCGHSA enrichment
- 2026-08-18 09:18 UTCEG score recompute
- 2026-08-18 09:18 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:47 UTCEG score recompute
- 2026-08-17 07:47 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:16 UTCEG score recompute
- 2026-08-16 06:16 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 04:46 UTCEG score recompute
- 2026-08-15 04:46 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 03:14 UTCEG score recompute
- 2026-08-14 03:14 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:44 UTCEG score recompute
- 2026-08-13 01:44 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 00:13 UTCGHSA enrichment
- 2026-08-10 22:42 UTCGHSA enrichment
Show 23 moreShow fewer
- 2026-08-09 21:10 UTCEG score recompute
- 2026-08-09 21:10 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 19:40 UTCEG score recompute
- 2026-08-08 19:40 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 18:09 UTCEG score recompute
- 2026-08-07 18:09 UTCGHSA enrichment
- 2026-08-06 16:38 UTCEG score recompute
- 2026-08-06 16:38 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 15:06 UTCEG score recompute▲ 1.70
- 2026-08-05 15:06 UTCGHSA enrichment
- 2026-08-05 15:06 UTCNVD updateCVSS v3 → 6.5
- 2026-08-04 19:30 UTCEG score recompute
- 2026-08-04 19:30 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 17:59 UTCEG score recompute
- 2026-08-03 17:59 UTCGHSA enrichment
- 2026-08-03 13:40 UTCEG score recompute
- 2026-08-03 12:39 UTCEG score recompute
- 2026-08-03 12:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-327
Frequently asked(5)
What is CVE-2026-56609?
When was CVE-2026-56609 disclosed?
Is CVE-2026-56609 actively exploited?
What is the CVSS score of CVE-2026-56609?
How do I remediate CVE-2026-56609?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56609
Is Your Infrastructure Affected by CVE-2026-56609?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.