HCL IntelliOps Event Management (IEM) is affected by a least privileges violation which could allow an attacker to access the resource with the elevated privilege that could not be accessed with the attacker's original privileges.
CVE-2025-62299
This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.6
- EG Score
- 6.6(low)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity66% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 20, 2026
Advisory Details (1)
Auto-updated Aug 20, 2026Security Bulletin: Multiple security vulnerabilities affect HCL IntelliOps Event Management (IEM) - Customer Support
https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0132456Vendor Advisories for CVE-2025-62299(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 13:23 UTCEG score recompute
- 2026-08-20 12:27 UTCEG score recompute
- 2026-08-20 12:26 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2025-62299?
When was CVE-2025-62299 disclosed?
What is the CVSS score of CVE-2025-62299?
How do I remediate CVE-2025-62299?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-62299
Is Your Infrastructure Affected by CVE-2025-62299?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.