Skip to main content
VulnerabilityPublished

CVE-2025-55205: projectcapsule capsule · Incorrect Authorization

Affects projectcapsule capsuleSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.10.4 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.10.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade projectcapsule capsule to 0.10.4.

Affected software

ProductAffectedFixed in
projectcapsule capsuleAffected
  • <0.10.4
Fixed in
  • 0.10.4

AI-suggested

European organizations should immediately upgrade Capsule to version 0.10.4 or later to remediate this vulnerability. Until the upgrade is applied, organizations should enforce strict access controls to limit tenant user permissions and monitor for suspicious label injection activities in system namespaces. Implementing Kubernetes Role-Based Access Control (RBAC) policies that restrict label modifications on system namespaces can provide temporary mitigation. Additionally, auditing and logging of namespace label changes should be enabled to detect potential exploitation attempts. Organizations should also review their tenant onboarding and authentication processes to ensure only trusted users have access to Capsule-managed clusters. Regular vulnerability scanning and penetration testing focused on multi-tenant isolation controls can help identify similar authorization weaknesses. Finally, educating DevOps and security teams about the risks of namespace label injection and the importance of applying security patches promptly is critical.

Description

Capsule is a multi-tenancy and policy-based framework for Kubernetes. A namespace label injection vulnerability in Capsule v0.10.3 and earlier allows authenticated tenant users to inject arbitrary labels into system namespaces (kube-system, default, capsule-system), bypassing multi-tenant isolation and potentially accessing cross-tenant resources through TenantResource selectors. This vulnerability enables privilege escalation and violates the fundamental security boundaries that Capsule is designed to enforce. This vulnerability is fixed in 0.10.4.

References

Community reviews

Loading reviews…