CVE-2026-10720GHSA-XG3J-C7Q4-F9PHGO-2026-5755
MicroCeph path traversal issue in the remote-import API
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 19.2.3+snapcf306793a4, 20.2.0+snapbe4e67380e, 0.0.0-20260609072127-5c2760d8fb76
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Canonical Microceph
From 19.2.1+snap74c0060321 · fixed in 19.2.3+snapcf306793a4; From 20.0.0 · fixed in 20.2.0+snapbe4e67380e
- github.com/canonical/microceph/microcephGo
fixed in 0.0.0-20260609072127-5c2760d8fb76