CVE-2025-62307

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-08-20. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

HCL IntelliOps Event Management (IEM) is affected by insufficient logging. Insufficient logging weakens accountability, obscures attack detection, and enables privilege probing.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/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 computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
No patch confirmed yet.
generic

Security Bulletin: Multiple security vulnerabilities affect HCL IntelliOps Event Management (IEM) - Customer Support

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0132456

Vendor Advisories for CVE-2025-62307(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 18× in last 7d / 78× 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.

  1. 2026-09-19 00:11 UTCEG score recompute
  2. 2026-09-19 00:11 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 22:07 UTCEG score recompute
  5. 2026-09-17 22:07 UTCGHSA enrichment
  6. 2026-09-17 19:30 UTCEPSS rescore
  7. 2026-09-16 20:03 UTCEG score recompute
  8. 2026-09-16 20:03 UTCGHSA enrichment
  9. 2026-09-16 14:07 UTCEPSS rescore
  10. 2026-09-15 14:48 UTCEG score recompute
  11. 2026-09-15 14:48 UTCGHSA enrichment
  12. 2026-09-15 03:10 UTCEPSS rescore
  13. 2026-09-14 12:44 UTCEG score recompute
  14. 2026-09-14 12:44 UTCGHSA enrichment
  15. 2026-09-13 16:46 UTCEPSS rescore
  16. 2026-09-13 10:25 UTCEG score recompute
  17. 2026-09-13 10:25 UTCGHSA enrichment
  18. 2026-09-12 15:00 UTCEPSS rescore
  19. 2026-09-12 08:21 UTCEG score recompute
  20. 2026-09-12 08:21 UTCGHSA enrichment
  21. 2026-09-11 14:52 UTCEPSS rescore
  22. 2026-09-11 09:36 UTCEPSS rescore
  23. 2026-09-11 06:16 UTCEG score recompute
  24. 2026-09-11 06:16 UTCGHSA enrichment
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 56 more
  1. 2026-09-10 04:12 UTCGHSA enrichment
  2. 2026-09-09 02:02 UTCEG score recompute
  3. 2026-09-09 02:02 UTCGHSA enrichment
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:00 UTCEPSS rescore
  6. 2026-09-07 11:23 UTCEG score recompute
  7. 2026-09-07 11:23 UTCGHSA enrichment
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 09:17 UTCEG score recompute
  10. 2026-09-06 09:17 UTCGHSA enrichment
  11. 2026-09-05 07:12 UTCEG score recompute
  12. 2026-09-05 07:12 UTCGHSA enrichment
  13. 2026-09-04 05:06 UTCEG score recompute
  14. 2026-09-04 05:06 UTCGHSA enrichment
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-03 02:28 UTCEG score recompute
  17. 2026-09-03 02:28 UTCGHSA enrichment
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-02 00:22 UTCEG score recompute
  20. 2026-09-02 00:22 UTCGHSA enrichment
  21. 2026-09-01 13:53 UTCEPSS rescore
  22. 2026-08-31 22:10 UTCGHSA enrichment
  23. 2026-08-30 20:06 UTCEG score recompute
  24. 2026-08-30 20:06 UTCGHSA enrichment
  25. 2026-08-30 19:16 UTCEPSS rescore
  26. 2026-08-30 01:21 UTCEPSS rescore
  27. 2026-08-29 18:03 UTCEG score recompute
  28. 2026-08-29 18:02 UTCGHSA enrichment
  29. 2026-08-28 21:40 UTCEPSS rescore
  30. 2026-08-28 15:54 UTCGHSA enrichment
  31. 2026-08-28 08:50 UTCEG score recompute
  32. 2026-08-28 08:50 UTCGHSA enrichment
  33. 2026-08-27 14:24 UTCEPSS rescore
  34. 2026-08-27 06:44 UTCEG score recompute
  35. 2026-08-27 06:44 UTCGHSA enrichment
  36. 2026-08-26 14:45 UTCEPSS rescore
  37. 2026-08-26 03:54 UTCEG score recompute
  38. 2026-08-26 03:54 UTCGHSA enrichment
  39. 2026-08-25 13:48 UTCEPSS rescore
  40. 2026-08-25 01:51 UTCEG score recompute
  41. 2026-08-25 01:51 UTCGHSA enrichment
  42. 2026-08-24 14:16 UTCEPSS rescore
  43. 2026-08-23 23:46 UTCEG score recompute
  44. 2026-08-23 23:46 UTCGHSA enrichment
  45. 2026-08-23 00:18 UTCEPSS rescore
  46. 2026-08-22 21:43 UTCEG score recompute
  47. 2026-08-22 21:43 UTCGHSA enrichment
  48. 2026-08-21 23:48 UTCEPSS rescore
  49. 2026-08-21 19:39 UTCGHSA enrichment
  50. 2026-08-20 17:34 UTCEG score recompute
  51. 2026-08-20 17:34 UTCGHSA enrichment
  52. 2026-08-20 16:52 UTCEG score recompute
  53. 2026-08-20 16:52 UTCGHSA enrichment
  54. 2026-08-20 12:19 UTCEG score recompute
  55. 2026-08-20 12:12 UTCEG score recompute
  56. 2026-08-20 12:11 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-62307?
CVE-2025-62307 is a medium vulnerability published on August 20, 2026. HCL IntelliOps Event Management (IEM) is affected by insufficient logging. Insufficient logging weakens accountability, obscures attack detection, and enables privilege probing.
When was CVE-2025-62307 disclosed?
CVE-2025-62307 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-62307 actively exploited?
CVE-2025-62307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.9% of all scored CVEs.
What is the CVSS score of CVE-2025-62307?
CVE-2025-62307 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2025-62307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-62307, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-62307

Explore →

Is Your Infrastructure Affected by CVE-2025-62307?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.