CVE-2026-35114: HCL AION · Information Exposure
Affects HCL AIONSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low.
Data as of 6 Nov 2026, 14:33 UTC
Thin evidence
One scorer or none| CNA (HCL) | CVSS 3.1 | 3.7 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL SoftwareHCL AION | Affected
| Fixed in– |
AI-suggested
Since the vulnerability involves missing or insecure HTTP headers, mitigation typically involves configuring the web server or application to include the X-Content-Type-Options header with the value 'nosniff'. This prevents browsers from MIME-sniffing responses and mitigates the vulnerability. Organizations using HCL AION should verify and update their HTTP response headers accordingly.
Description
HCL AION has a vulnerability due to the absence or insecurity of the X-Content-Type-Options header. This allows browsers to MIME-sniff responses, which can lead to content being interpreted as an unintended type. Under certain conditions, this behavior may cause unintended effects or security impacts. The vulnerability is classified as CWE-200, indicating exposure of sensitive information to unauthorized actors. The CVSS score is 3.7, reflecting a low severity level.