Capsule vulnerable to privilege escalation by ServiceAccount deployed in a Tenant Namespace

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-46167: 0.94% estimated exploitation activity in the next 30 days; percentile 61.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Capsule implements a multi-tenant and policy-based environment in a Kubernetes cluster. A ServiceAccount deployed in a Tenant Namespace, when granted with PATCH capabilities on its own Namespace, is able to edit it and remove the Owner Reference, breaking the reconciliation of the Capsule Operator and removing all the enforcement like Pod Security annotations, Network Policies, Limit Range and Resource Quota items. With that said, an attacker could detach the Namespace from a Tenant that is forbidding starting privileged Pods using the Pod Security labels by removing the OwnerReference, removing the enforcement labels, and being able to start privileged containers that would be able to start a generic Kubernetes privilege escalation. Patches Patches have been released for version 0.1.3 and all users must upgrade to this release. Workarounds N.A. References N.A. For more information If you have any questions or comments about this advisory: Open an issue in github.com/clastix/capsule…

Published by the source

5 Dec 2022, 23:08 UTC

Last modified by the source

31 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x45c-cvp8-q4fm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-46167

Advisory: Capsule vulnerable to privilege escalation by ServiceAccount deployed in a Tenant Namespace
IDs: CVE-2022-46167, GHSA-x45c-cvp8-q4fm
Record: https://patchnext.com/advisories/cve-2022-46167 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/clastix/capsule 0.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/clastix/capsule: affected <= 0.1.2; fixed in 0.1.3

## Suggested inspection (read-only)
- Go github.com/clastix/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/clastix/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://github.com/advisories/GHSA-x45c-cvp8-q4fm (GitHub-reviewed advisory GHSA-x45c-cvp8-q4fm lists affected ranges: Go github.com/clastix/capsule >=0 <=0.1.2)

Commands are suggestions: review each one before running it.