Categories
CVE-2026-65835 medium CVSS 6.6

Privilege Escalation in github.com/projectcapsule/capsule (CVE-2026-65835)

Summary

Vulnerability in github.com/projectcapsule/capsule (CVE-2026-65835). Risk of unauthorized operations or information disclosure. Exploitable via ClusterRole. Mitigation: upgrade to 0.13.8 or later.

Original description

The description as published by the source.

Summary

CVE-2026-22872 (GHSA-qjjm-7j9w-pw72) reported that a Tenant Owner could create cluster-scoped resources
(e.g. ClusterRole, ValidatingWebhookConfiguration) through a TenantResource, because the controller
applies them with its cluster-admin ServiceAccount and SetNamespace is ineffective for cluster-scoped
kinds. The v0.13.0 fix added a cluster-scope rejection guard, but only on the NamespacedItems selection
path
(ResourceReference.LoadResources -> IsNamespacedGVK, error "cluster-scoped kind ... is not allowed"). The RawItems create path — the exact vector the original advisory named — and the Generators
path were not given this guard.
The vulnerability therefore persists in all releases v0.13.0 through
v0.13.7
and on trunk HEAD (8d89d6865d).

Details

TenantResource reconcile flow:

  • internal/controllers/resources/namespaced.go reconcile() obtains the apply client via loadClient();
    by default (impersonation off, no Spec.ServiceAccount) this is the manager client whose SA is bound to
    cluster-admin (charts/capsule/templates/rbac.yaml:488-501, {fullname}-manager-rolebinding ->
    roleRef cluster-admin).
  • Collector.Collect() (collect.go) processes spec.RawItems via handleRawItem and spec.Generators
    via handleGeneratorItem.

handleRawItem (collect.go:406-425, trunk HEAD — byte-identical to v0.13.0):

tmplString := tpl.FastTemplate(string(item.Raw), opts.Iterator.FastContext)
obj := &unstructured.Unstr…

Source: NIST National Vulnerability Database 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-65835 has been found in github.com/projectcapsule/capsule.
Attackers can target a specific entry point like ClusterRole over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.6/10.
What to do: upgrade github.com/projectcapsule/capsule to 0.13.8 or later.
If unsure, ask your IT team or search "github.com/projectcapsule/capsule CVE-2026-65835" on the vendor's site.

CVE-2026-65835 (github.com/projectcapsule/capsule) — CWE-269 / CVSS v3 6.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ClusterRole / ValidatingWebhookConfiguration / TenantResource / SetNamespace
Patched: 0.13.8 — 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.

❓ What is the problem

A vulnerability (CWE-269) exists in github.com/projectcapsule/capsule. Attackers reach the vulnerable code path via ClusterRole.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/projectcapsule/capsule. Attack surface: ClusterRole / ValidatingWebhookConfiguration / TenantResource / SetNamespace.

🔥 Severity

Severity: Medium (CVSS 6.6/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.13.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/projectcapsule/capsule to 0.13.8

    ステージング環境で 0.13.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/projectcapsule/capsule
[{"type":"SEMVER","events":[{"introduced":"0.13.0"},{"fixed":"0.13.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details