CVE-2026-16792

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreHIGH confidence

Score 6.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. a secondary CVSS source baseline 6.1; sources differ by 0.0.

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

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

An improper certificate validation vulnerability was reported in multiple Lenovo XClarity Orchestrator (LXCO) 2.2.0 microservices that could allow an adjacent network attacker to intercept sensitive communications by performing a machine-in-the-middle attack against HTTPS connections during TLS certificate validation under certain circumstances.

CVSS v3
6.1
EG Score
6.1(high)
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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 5, 2026

References (1)

Vendor Advisories for CVE-2026-16792(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 10× in last 7d / 36× 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-20 22:25 UTCGHSA enrichment
  2. 2026-08-19 22:04 UTCGHSA enrichment
  3. 2026-08-18 21:43 UTCGHSA enrichment
  4. 2026-08-17 20:49 UTCGHSA enrichment
  5. 2026-08-16 20:28 UTCGHSA enrichment
  6. 2026-08-15 20:07 UTCEG score recompute
  7. 2026-08-15 20:07 UTCGHSA enrichment
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 19:45 UTCEG score recompute
  10. 2026-08-14 19:45 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 19:24 UTCGHSA enrichment
  13. 2026-08-12 19:02 UTCEG score recompute
  14. 2026-08-12 19:02 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 18:40 UTCEG score recompute
  17. 2026-08-11 18:40 UTCGHSA enrichment
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-10 18:19 UTCGHSA enrichment
  20. 2026-08-09 17:55 UTCGHSA enrichment
  21. 2026-08-08 17:35 UTCEG score recompute
  22. 2026-08-08 17:35 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-07 17:13 UTCEG score recompute
  25. 2026-08-07 17:13 UTCGHSA enrichment
Show 11 more
  1. 2026-08-06 16:52 UTCEG score recompute
  2. 2026-08-06 16:52 UTCGHSA enrichment
  3. 2026-08-06 13:46 UTCEPSS rescore
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-05 16:31 UTCEG score recompute
  6. 2026-08-05 16:31 UTCGHSA enrichment
  7. 2026-08-05 15:29 UTCEG score recompute
  8. 2026-08-05 15:29 UTCGHSA enrichment
  9. 2026-08-04 20:32 UTCEG score recompute
  10. 2026-08-04 20:06 UTCEG score recompute
  11. 2026-08-04 20:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16792?
CVE-2026-16792 is a medium vulnerability published on August 4, 2026. An improper certificate validation vulnerability was reported in multiple Lenovo XClarity Orchestrator (LXCO) 2.2.0 microservices that could allow an adjacent network attacker to intercept sensitive communications by performing a machine-in-the-middle attack against HTTPS connections during TLS…
When was CVE-2026-16792 disclosed?
CVE-2026-16792 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16792 actively exploited?
CVE-2026-16792 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-16792?
CVE-2026-16792 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-16792?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16792, 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-16792

Explore →

Is Your Infrastructure Affected by CVE-2026-16792?

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

Start Free Scan →Browse All CVEs