CVE-2026-35110 · Other
NO FIX YET
HCL AION does not enforce encrypted HTTPS for every request, so some traffic can travel unencrypted. An attacker on the network path could intercept data sent over those connections.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that run HCL AION and send requests across networks an attacker could observe. The sources do not say which endpoints or configurations are affected, so the exposure cannot be narrowed further from this signal.
Not affected if unknown
Who cares hcl-aion, self-hosted
Unknown from the sources.
No fix yet, per the sources.
HCL AION is affected by a vulnerability where encrypted (HTTPS) communication was not enforced for all requests. Data may be transmitted over unencrypted connections and intercepted by an attacker on the network, potentially resulting in unintended behavior or security impact under certain conditions.
This page as .md · .json · CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.