CVE-2026-35110

HCL AION permits unencrypted application requests

HCL Software · HCL AION

First documented disclosure · Review checkpoint

Summary

Encrypted connections are not enforced for all requests. Traffic may be exposed or altered in transit.

Severity and exploitation evidence

Medium · 5.4/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed public sources describe the vulnerability and its conditions. Malicious exploitation has not been established in the reviewed sources.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Transport encryption is not enforced for every application request.

Conditions required

An observer needs a suitable network position and a user must communicate through an affected path.

Potential impact

Traffic may be exposed or altered in transit.

Affected versions and configurations

2.6.0.

Fix and mitigation status

2.8.0.

Practical next steps

Upgrade HCL AION to 2.8.0 and verify the affected control in the deployed interface.

Operating lesson

Enforce encrypted transport on every reachable application path.

Evidence and limits

HCL bulletin KB0135118 was published 2026-11-04 and identifies 2.8.0 as the fix. HCL’s CVE record gives 2026-11-03 as its public date.

Sources