What is the CVSS score of CVE-2026-65835?

CVE-2026-65835 has a CVSS 3.1 base score of 6.6 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2026-65835?

Yes, a public proof-of-concept exploit is available for CVE-2026-65835. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2026-65835?

Yes, a patch is available for CVE-2026-65835. Update the affected software to the latest version immediately.

Capsule CVE-2026-65835

EUVD-2026-51296 MEDIUM

Improper Privilege Management (CWE-269)

2026-07-30 GitHub_M

GHSA-jr6p-8pjj-mfx6

Kubernetes Privilege Escalation Capsule

6.6

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

6.6 MEDIUM

AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L

vuln.today AI

9.1 CRITICAL

Creating ClusterRoleBinding directly grants cluster-admin, yielding immediate C:H/I:H/A:H across the full cluster scope.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

Patch available

Jul 30, 2026 - 21:04 EUVD

Source Code Evidence Fetched

Jul 30, 2026 - 20:53 vuln.today

Analysis Generated

Jul 30, 2026 - 20:53 vuln.today

DescriptionCVE.org

Capsule is a multi-tenancy and policy-based framework for Kubernetes. From 0.13.0 until 0.13.8, after the incomplete CVE-2026-22872 fix, TenantResource RawItems and Generators in internal/controllers/resources/collect.go, including handleRawItem and handleGeneratorItem, did not apply the ResourceReference.LoadResources and IsNamespacedGVK cluster-scoped resource rejection guard used by NamespacedItems, allowing a Tenant Owner to create cluster-scoped resources such as ClusterRole or ValidatingWebhookConfiguration through the cluster-admin controller client. This issue is fixed in version 0.13.8.

AnalysisAI

Privilege escalation in Capsule (Kubernetes multi-tenancy framework) versions 0.13.0-0.13.7 allows authenticated Tenant Owners to break out of tenant isolation and create cluster-scoped Kubernetes resources - including ClusterRole, ClusterRoleBinding, and ValidatingWebhookConfiguration - through the cluster-admin controller client. This is an incomplete fix of CVE-2026-22872: the TenantResource RawItems and Generators code paths (handleRawItem, handleGeneratorItem) were never updated to enforce the same cluster-scoped resource rejection guards applied to NamespacedItems. No public exploit or CISA KEV listing has been identified at time of analysis; vendor-released patch v0.13.8 is available.

Technical ContextAI

Capsule (CPE: cpe:2.3:a:projectcapsule:capsule:*:*:*:*:*:*:*:*) is a Kubernetes operator implementing multi-tenancy via Tenant custom resources, enforcing namespace isolation and policy boundaries. The root cause is CWE-269 (Improper Privilege Management): the resource collection logic in internal/controllers/resources/collect.go exposes two code paths - handleRawItem (for TenantResource RawItems) and handleGeneratorItem (for Generators) - that were not updated during the CVE-2026-22872 remediation effort. The guard functions ResourceReference.LoadResources and IsNamespacedGVK, which reject cluster-scoped resource kinds, were added only to the NamespacedItems path. As a result, the RawItems and Generators paths use the cluster-admin controller client without validating whether the target GroupVersionKind is cluster-scoped, allowing tenant-level manifests to instantiate objects such as ClusterRole, ClusterRoleBinding, and ValidatingWebhookConfiguration at cluster scope.

RemediationAI

Vendor-released patch: v0.13.8. Upgrade Capsule to v0.13.8 immediately; the Docker image ghcr.io/projectcapsule/capsule:0.13.8 and Helm chart for this version are available at https://github.com/projectcapsule/capsule/releases/tag/v0.13.8. If immediate upgrade is not possible, a targeted compensating control is to revoke TenantResource RBAC permissions from Tenant Owners - specifically the ability to create or update TenantResource objects - until patching is complete; this disables the vulnerable feature entirely but also removes legitimate TenantResource functionality. Alternatively, admission webhook policies (e.g., OPA/Gatekeeper or Kyverno) can be configured to reject TenantResource manifests containing RawItems or Generator blocks referencing cluster-scoped GVKs (ClusterRole, ValidatingWebhookConfiguration, etc.), acting as a defense-in-depth layer. Note that either workaround may break legitimate multi-tenancy workflows that rely on TenantResource for resource propagation.