CyberSecBulletin
CVE-2025-31952NVD status: Analyzed

HCL iAutomate is affected by an insufficient session expiration.

Published Updated By the CyberSecBulletin desk

CVE-2025-31952 is a high-severity vulnerability in iAutomate from HCL Software, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected iAutomate versions: 6.5.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.38% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of iAutomate you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on support.hcl-software.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
HCL SoftwareiAutomate6.5.1Not stated
HCL SoftwareDryice Iautomate6.5.1Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L. Scored by CNA (hcl.com).

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Spotted an error? Tell us.