CVE-2026-35111: HCL AION · Information Exposure
Affects HCL AIONSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 6 Nov 2026, 13:34 UTC
Thin evidence
One scorer or none| CNA (HCL) | CVSS 3.1 | 4.8 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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 CORP headers, remediation typically involves configuring the application to send appropriate Cross-Origin-Resource-Policy headers to restrict resource loading to trusted origins. Monitor vendor advisories for any official patches or updates.
Description
HCL AION has a vulnerability due to a missing or insecure Cross-Origin-Resource-Policy (CORP) header. This flaw allows application resources to be loaded by other origins, which can lead to cross-origin data leakage. The vulnerability may cause unintended behavior or security impact under certain conditions. The CVSS score is 4.8, indicating a medium severity level.