Vulnerability in github.com/canonical/microceph/microceph (CVE-2026-10720)
Summary
Vulnerability in github.com/canonical/microceph/microceph (CVE-2026-10720). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.0-20260609072127-5c2760d8fb76 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10720 has been found in github.com/canonical/microceph/microceph.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/canonical/microceph/microceph to 0.0.0-20260609072127-5c2760d8fb76 or later.
If unsure, ask your IT team or search "github.com/canonical/microceph/microceph CVE-2026-10720" on the vendor's site.
CVE-2026-10720 (github.com/canonical/microceph/microceph) — CWE-23
Patched: 0.0.0-20260609072127-5c2760d8fb76 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-23) exists in github.com/canonical/microceph/microceph.
Check the vendor advisory for the affected versions of github.com/canonical/microceph/microceph.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260609072127-5c2760d8fb76.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/canonical/microceph/microceph' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/canonical/microceph/microceph' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/canonical/microceph/microcephを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/canonical/microceph/microceph to 0.0.0-20260609072127-5c2760d8fb76ステージング環境で 0.0.0-20260609072127-5c2760d8fb76 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com