CVE-2026-10720

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.1Exploit: NoneExposed: 0

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

Canonical MicroCeph versions from the squid and tentacle track are vulnerable to a path traversal issue in the remote-import API. Holders of a trusted cluster mTLS certificate (such as enrolled cluster members) or join token can manipulate files in an imported remote cluster within the /var/snap/microceph confinement. This would allow daemon disruption and pollution of the cluster state.

CVSS v3
5.1
EG Score
5.1(medium)
EPSS
11.0%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

fix: check remote paths (CVE-2026-10720)

Fix merged in canonical/microceph PR #758 on 2026-06-09 — awaiting tagged release

https://github.com/canonical/microceph/pull/758

Vendor Advisories for CVE-2026-10720(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/canonical/microceph/microceph—0.0.0-20260609072127-5c2760d8fb76—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× 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-07-07 08:12 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 10:25 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 12:28 UTCEG score recompute
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 14:46 UTCEG score recompute
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 17:03 UTCEG score recompute
  11. 2026-07-02 19:19 UTCEG score recompute
  12. 2026-07-01 21:37 UTCEG score recompute
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:55 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 02:13 UTCEG score recompute
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 04:31 UTCEG score recompute
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 06:48 UTCEG score recompute
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 09:05 UTCEG score recompute
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 11 more
  1. 2026-06-26 11:23 UTCEG score recompute
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-25 10:49 UTCEG score recompute
  4. 2026-06-24 14:05 UTCEPSS rescore
  5. 2026-06-24 13:07 UTCEG score recompute
  6. 2026-06-23 21:32 UTCEPSS rescore
  7. 2026-06-23 15:22 UTCEG score recompute
  8. 2026-06-22 17:39 UTCEG score recompute▲ 5.10
  9. 2026-06-22 17:37 UTCNVD updateCVSS v3 → 5.1 · CVSS v4 → 5.1
  10. 2026-06-19 06:57 UTCEG score recompute
  11. 2026-06-19 06:57 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10720?
CVE-2026-10720 is a medium vulnerability published on June 19, 2026. Canonical MicroCeph versions from the squid and tentacle track are vulnerable to a path traversal issue in the remote-import API. Holders of a trusted cluster mTLS certificate (such as enrolled cluster members) or join token can manipulate files in an imported remote cluster within the…
When was CVE-2026-10720 disclosed?
CVE-2026-10720 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10720 actively exploited?
CVE-2026-10720 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10720?
CVE-2026-10720 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-10720?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10720, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10720

Explore →

Is Your Infrastructure Affected by CVE-2026-10720?

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

Start Free Scan →Browse All CVEs