Data exposure and alteration via legacy TLS
Published Aug 3, 2026 · Updated Aug 3, 2026
Weak transport encryption in HCL iControl 3.2.0 allows remote attackers to read or alter data in transit via legacy TLS connections. The application's TLS endpoint accepts TLS 1.0 and TLS 1.1, negotiating obsolete protocols whose known weaknesses undermine confidentiality and integrity. Exploitation is unauthenticated and remote, but requires a client connection using one of those protocols and attack conditions suitable for compromising it.
Summary
What happened
Weak transport encryption in HCL iControl 3.2.0 allows remote attackers to read or alter data in transit via legacy TLS connections. The application's TLS endpoint accepts TLS 1.0 and TLS 1.1, negotiating obsolete protocols whose known weaknesses undermine confidentiality and integrity. Exploitation is unauthenticated and remote, but requires a client connection using one of those protocols and attack conditions suitable for compromising it.
The record
- CVE
- CVE-2026-56609
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- HCL Software
- Product
- HCL iControl
- Classifications
- CWE-327, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v3.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo