HCL AION version 2 is affected by a JWT Token Expiry Too Long vulnerability.

published 2026-01-19 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-3207

cvss: 2.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits: 0; none known

HCL AION version 2 is affected by a JWT Token Expiry Too Long vulnerability. This may increase the risk of token misuse, potentially resulting in unauthorized access if the token is compromised.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 9 mo ago (2026-01-20)

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	2.4	CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

HCL Software AION

Classification

Weakness

CWE-613 DEPRECATED: Insufficient Session Expiration

References

support.hcl-software.com /kb_view.do?sys_kb_id=4b92474633de7ad4159a05273e5c7b4b&searchTerm=kb0127995#
vendor-advisory

Sources

CVE List CVE-2025-52661
NVD CVE-2025-52661

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary