Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-56609: CWE-327 Use of a Broken or Risky Cryptographic Algorithm in HCL Software HCL iControl

0
Medium
VulnerabilityCVE-2026-56609cvecve-2026-56609cwe-327
Published: 08/03/2026 (08/03/2026, 11:26:07 UTC)
Source: CVE Database V5
Vendor/Project: HCL Software
Product: HCL iControl

Description

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.

CVSS v3.1

Score 4.8medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected software

Affected versions
=3.2.0v3.2.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/03/2026, 13:08:16 UTC

Technical Analysis

CVE-2026-56609 identifies a vulnerability in HCL iControl version 3.2.0 where weak SSL/TLS versions (TLS 1.0 and 1.1) are supported. These protocols are deprecated and vulnerable to known cryptographic attacks, potentially allowing attackers to intercept or manipulate sensitive data in transit. The vulnerability is categorized under CWE-327, reflecting the use of broken or risky cryptographic algorithms. No official patch or remediation guidance has been provided by the vendor as of the published date.

Potential Impact

The use of weak TLS versions in HCL iControl 3.2.0 can lead to exposure of sensitive information during network communications. While the CVSS score indicates a medium impact, the vulnerability primarily affects confidentiality and integrity of data in transit. There are no known exploits in the wild reported at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, it is recommended to disable support for TLS 1.0 and 1.1 in the affected application if possible, and configure the system to use stronger protocols such as TLS 1.2 or TLS 1.3. Monitor vendor communications for updates on patches or official mitigations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
HCL
Date Reserved
2026-06-22T13:40:09.127Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a708e2fbf32cb7a349a24f7

Added to database: 08/03/2026, 12:48:47 UTC

Last enriched: 08/03/2026, 13:08:16 UTC

Last updated: 08/03/2026, 13:33:36 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses