CVE-2025-31952: HCL Software iAutomate · Insufficient Session Expiration
Affects HCL Software iAutomateSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL Software iAutomate | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-31952, European organizations should implement the following specific measures: 1) Immediately review and enforce strict session token revocation policies, ensuring that tokens are manually revoked promptly when no longer needed or when suspicious activity is detected. 2) Implement compensating controls such as network segmentation and strict access controls around iAutomate instances to limit exposure if tokens are compromised. 3) Enhance monitoring and logging of session token usage to detect anomalous or prolonged sessions that may indicate exploitation. 4) Where possible, integrate multi-factor authentication (MFA) to reduce the risk of token theft leading to unauthorized access. 5) Engage with HCL Software to obtain patches or updates addressing this vulnerability; if patches are unavailable, consider upgrading to a version that includes proper session expiration mechanisms. 6) Educate users and administrators on the risks of token reuse and the importance of session management hygiene. 7) Regularly audit active sessions and revoke any that appear stale or suspicious. These steps go beyond generic advice by focusing on operational controls tailored to the specific weakness of indefinite token validity.
Description
HCL iAutomate is affected by an insufficient session expiration. This allows tokens to remain valid indefinitely unless manually revoked, increasing the risk of unauthorized access.