Skip to main content
VulnerabilityPublished

CVE-2025-0249: HCL Software IEM · Improper Authentication

Affects HCL Software IEMSource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jul 2025

  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
HCL Software IEMAffected
  • =1.2
Fixed in–

AI-suggested

  1. Implement strict privilege management and monitoring to detect and prevent misuse of high-privilege accounts, as exploitation requires such privileges.
  2. Enforce short token lifetimes and implement manual or automated token revocation mechanisms where possible, to minimize the window of opportunity for token reuse.
  3. Monitor logs for unusual token reuse or session anomalies that could indicate exploitation attempts.
  4. Apply network segmentation and access controls to limit exposure of HCL IEM systems to only trusted and necessary users and devices.
  5. Engage with HCL Software support to obtain official patches or updates addressing this vulnerability as soon as they become available.
  6. Consider implementing additional authentication layers or session management controls external to HCL IEM to compensate for the token invalidation weakness.
  7. Conduct regular security audits and penetration tests focusing on authentication and session management within the HCL IEM environment.

Description

HCL IEM is affected by an improper invalidation of access or JWT token vulnerability.  A token was not invalidated which may allow attackers to access sensitive data without authorization.

References

Community reviews

Loading reviews…