Vulnerability in github.com/projectcapsule/capsule (CVE-2026-22872)
Summary
Vulnerability in github.com/projectcapsule/capsule (CVE-2026-22872). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.13.0 or later.
Original description
The description as published by the source.
Capsule is a multi-tenancy and policy-based framework for Kubernetes. The Capsule Controller runs with cluster-admin privileges. Although the TenantResource RawItems processing logic forcibly sets the namespace, this is ineffective for cluster-scoped resources. Prior to version 0.13.0, tenant administrators can leverage the Controller's elevated privileges to create cluster-scoped resources (such as ClusterRole and ValidatingWebhookConfiguration) that they cannot create directly, achieving cross-tenant privilege escalation and cluster-level attacks. The attack vector has a few limiting factors. This attack requires Tenant Owner privileges and requires Capsule Controller running with cluster-admin privileges (default configuration). Additionally, some clusters may have additional admission controllers blocking malicious resources. Version 0.13.0 patches this issue.
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-22872 has been found in github.com/projectcapsule/capsule.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: upgrade github.com/projectcapsule/capsule to 0.13.0 or later.
If unsure, ask your IT team or search "github.com/projectcapsule/capsule CVE-2026-22872" on the vendor's site.
CVE-2026-22872 (github.com/projectcapsule/capsule) — CWE-20 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.13.0 — 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-20) exists in github.com/projectcapsule/capsule.
Check the vendor advisory for the affected versions of github.com/projectcapsule/capsule.
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover.
Update to 0.13.0.
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/projectcapsule/capsule' . 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/projectcapsule/capsule' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/projectcapsule/capsuleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/projectcapsule/capsule to 0.13.0ステージング環境で 0.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com