Skip to main content
VulnerabilityPublished

CVE-2025-52626: HCL AION · OS Command Injection

Affects HCL AIONSource CVE Database V5

0

Not known to be exploited · CVSS 4.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
HCLAIONAffected
  • =2.0
Fixed in–

AI-suggested

  1. Restrict local access to systems running HCL AION 2.0 by enforcing strict access controls and monitoring user activities.
  2. Implement application-level input validation and sanitization to prevent injection of malicious commands.
  3. Use host-based intrusion detection systems (HIDS) to detect unusual command execution patterns.
  4. Apply the vendor's patches promptly once they become available; monitor HCL security advisories for updates.
  5. Conduct regular security audits and penetration tests focusing on local privilege abuse scenarios.
  6. Employ the principle of least privilege to limit user permissions on affected systems.
  7. Isolate critical systems running HCL AION from less trusted network segments to reduce attack surface.
  8. Educate system administrators and users about the risks of local command injection and suspicious activities.
  9. Maintain up-to-date backups to recover quickly from potential system compromises.
  10. Consider deploying application whitelisting to restrict execution of unauthorized commands or scripts.

Description

A Potential Command Injection vulnerability in HCL AION.  An This can allow unintended command execution, potentially leading to unauthorized actions on the underlying system.This issue affects AION: 2.0

References

Community reviews

Loading reviews…