Capsule has an incomplete fix of CVE-2026-22872: TenantResource RawItems and Generators still allow cluster-scoped resource creation (cross-tenant privilege escalation)
CVE-2026-65835GHSA-jr6p-8pjj-mfx6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/projectcapsule/capsule 0.13.8), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/projectcapsule/capsule
- Affected
- >= 0.13.0, <= 0.13.7
- Fixed in
- 0.13.8
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jr6p-8pjj-mfx6 lists affected ranges: Go github.com/projectcapsule/capsule >=0.13.0 <0.13.8 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6157 lists affected ranges: Go github.com/projectcapsule/capsule >=0.13.0 <0.13.8 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jr6p-8pjj-mfx6 lists affected ranges: Go github.com/projectcapsule/capsule >=0.13.0 <=0.13.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.6 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
- EPSS
- CVE-2026-65835: 0.24% estimated exploitation activity in the next 30 days; percentile 14.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-jr6p-8pjj-mfx6
- Revision 2 · amended ·
Amended from osv record GO-2026-6157
- Revision 1 · created ·
Published from osv record GHSA-jr6p-8pjj-mfx6
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-65835 Advisory: Capsule has an incomplete fix of CVE-2026-22872: TenantResource RawItems and Generators still allow cluster-scoped resource creation (cross-tenant privilege escalation) IDs: CVE-2026-65835, GHSA-jr6p-8pjj-mfx6 Record: https://patchnext.com/advisories/cve-2026-65835 (revision 3, source checked 26 Oct 2026, 15:28 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/projectcapsule/capsule 0.13.8. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/projectcapsule/capsule: affected >= 0.13.0, <= 0.13.7; fixed in 0.13.8 ## Suggested inspection (read-only) - Go github.com/projectcapsule/capsule: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/projectcapsule/capsule. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-jr6p-8pjj-mfx6 (OSV record GHSA-jr6p-8pjj-mfx6 lists affected ranges: Go github.com/projectcapsule/capsule >=0.13.0 <0.13.8 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6157 (OSV record GO-2026-6157 lists affected ranges: Go github.com/projectcapsule/capsule >=0.13.0 <0.13.8 (fixed)) - Verified: https://github.com/advisories/GHSA-jr6p-8pjj-mfx6 (GitHub-reviewed advisory GHSA-jr6p-8pjj-mfx6 lists affected ranges: Go github.com/projectcapsule/capsule >=0.13.0 <=0.13.7) Commands are suggestions: review each one before running it.
Loading voting…