CVE-2025-52661: HCL AION version 2 is affected by a JWT Token Expiry Too Long vulnerability

Routine

LOW 2.4DOWNGRADE

CVE-2025-52661 is a low-severity flaw (CVSS 2.4) affecting aion. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	2.4 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-613
Published	2026-01-19
Last modified	2026-06-17

Publisher (CNA): HCL Software · Vendor: hcltech

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-19 18:16 UTCPublished CVE record published
2026-06-17 09:36 UTCUpdated Record last modified

hcltech aion DOWNGRADE

Affected: 2.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy aion || rpm -q aion || aion --version

2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison aion sudo apt install aion=<VERSION_BEFORE_2.0.0> sudo apt-mark hold aion

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list aion sudo dnf downgrade aion-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add aion

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-52661?

aion: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-52661 being exploited?

CVE-2025-52661 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-52661 affect?

CVE-2025-52661 affects aion. Severity is low (CVSS 2.4). 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.

How urgent is CVE-2025-52661?

Priority 10/100. No elevated risk signals yet.

Related CVEs

CVE-2025-52641 LOW 2.9 UPGRADE HCL AION is affected by a vulnerability where certain system behaviours may allow exploration of internal file
CVE-2025-55252 LOW 3.1 DOWNGRADE HCL AION version 2 is affected by a Weak Password Policy vulnerability
CVE-2025-55251 LOW 3.1 DOWNGRADE HCL AION is affected by an Unrestricted File Upload vulnerability
CVE-2025-55250 LOW 1.8 DOWNGRADE HCL AION version 2 is affected by a Technical Error Disclosure vulnerability
CVE-2025-55249 LOW 3.5 DOWNGRADE HCL AION is affected by a Missing Security Response Headers vulnerability

References

← Back to latest CVEs