CVE-2026-56567

MEDIUMNVD 3.35.1▲
EchelonGraph scoreMEDIUM confidence

Score 5.1 from GitHub Security Advisory published 2026-07-31. NVD baseline CVSS 3.3; sources differ by 1.8.

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

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

HCL iControl v4.3.0 was affected by Security Misconfiguration vulnerabilities. It involves the public exposure of internal configuration files due to improper web server or application hardening.

CVSS v3
3.3
EG Score
5.1(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity51% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 6, 2026

Advisory Details (1)

Auto-updated Jul 31, 2026
No patch confirmed yet.
generic

Security Bulletin: Multiple security vulnerabilities affect HCL iControl - Customer Support

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

Vendor Advisories for CVE-2026-56567(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 17× in last 7d / 49× 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-08-19 17:04 UTCEPSS rescore
  2. 2026-08-19 14:49 UTCEG score recompute
  3. 2026-08-19 14:49 UTCGHSA enrichment
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-18 12:52 UTCEG score recompute
  6. 2026-08-18 12:52 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 10:51 UTCGHSA enrichment
  9. 2026-08-16 08:54 UTCEG score recompute
  10. 2026-08-16 08:54 UTCGHSA enrichment
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 06:57 UTCEG score recompute
  13. 2026-08-15 06:57 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 04:42 UTCEG score recompute
  16. 2026-08-14 04:42 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 02:44 UTCEG score recompute
  19. 2026-08-13 02:44 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-12 00:47 UTCEG score recompute
  22. 2026-08-12 00:47 UTCGHSA enrichment
  23. 2026-08-10 22:50 UTCGHSA enrichment
  24. 2026-08-09 20:53 UTCGHSA enrichment
  25. 2026-08-08 18:56 UTCEG score recompute
Show 24 more
  1. 2026-08-08 18:56 UTCGHSA enrichment
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 16:59 UTCEG score recompute
  4. 2026-08-07 16:59 UTCGHSA enrichment
  5. 2026-08-06 15:02 UTCEG score recompute
  6. 2026-08-06 15:02 UTCGHSA enrichment
  7. 2026-08-06 15:01 UTCNVD updateCVSS v3 → 3.3 · severity → LOW
  8. 2026-08-06 13:47 UTCEPSS rescore
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-05 14:31 UTCEG score recompute
  11. 2026-08-05 14:31 UTCGHSA enrichment
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 12:34 UTCGHSA enrichment
  14. 2026-08-04 00:12 UTCEG score recompute
  15. 2026-08-04 00:11 UTCGHSA enrichment
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 22:14 UTCEG score recompute
  18. 2026-08-02 22:14 UTCGHSA enrichment
  19. 2026-08-02 02:27 UTCEPSS rescore
  20. 2026-08-01 20:17 UTCEG score recompute
  21. 2026-08-01 20:17 UTCGHSA enrichment
  22. 2026-07-31 16:29 UTCEG score recompute
  23. 2026-07-31 15:34 UTCEG score recompute
  24. 2026-07-31 15:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56567?
CVE-2026-56567 is a medium vulnerability published on July 31, 2026. HCL iControl v4.3.0 was affected by Security Misconfiguration vulnerabilities. It involves the public exposure of internal configuration files due to improper web server or application hardening.
When was CVE-2026-56567 disclosed?
CVE-2026-56567 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56567 actively exploited?
CVE-2026-56567 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 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-56567?
CVE-2026-56567 has a CVSS v3 base score of 3.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.1.
How do I remediate CVE-2026-56567?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56567, 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-2026-56567

Explore →

Is Your Infrastructure Affected by CVE-2026-56567?

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

Start Free Scan →Browse All CVEs