CVE-2026-5345HCL AION missing encryption
CVE-2026-5345 is a missing encryption in HCL AION, rated low (3.7 on CVSS 3.1).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
Sensitive data is sent or stored without encryption.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place HCL AION runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
HCL AION is affected by a missing encryption vulnerability in a second WebSocket connection defined in the GenAI web interface. The connection used the unencrypted WebSocket protocol (ws://test) instead of an encrypted (wss://) channel. This may allow data exchanged over the connection to be intercepted or read by an attacker on the network, potentially resulting in unintended behavior or security impact under certain conditions.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
- Signature checks. The flaw sits on the network path between clients and services.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.
Questions to answer about your own systems
- Where does HCL AION run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.