Capsule tenant owner with "patch namespace" permission can hijack system namespaces

Exploitation

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

CVSS 4.0

8.6 · CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · score source

EPSS

• CVE-2024-39690: 0.54% estimated exploitation activity in the next 30 days; percentile 45.52 (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.

Attack Vector Then, let me briefly explain the reasons for the errors mentioned above: 1. The 'kubectl edit' command was used to patch the namespace, but this operation requires both 'get' and 'patch' permissions, hence the error. One should use methods like 'curl' to directly send a PATCH request; 2. The webhook does not intercept patch operations on 'kube-system' because 'kube-system' does not have an ownerReference. Below are my detailed reproduction steps 1. Create a test cluster kind create cluster --image=kindest/node:v1.24.15 --name=k8s 2. Install the capsule helm install capsule projectcapsule/capsule -n capsule-system --create-namespace 3. Create a tenant 4. Create user alice 5. Patch kube-system (The first command is executed in the current shell, while the 2nd and 3rd commands require a different shell window because the current shell is being used as a proxy.) 7. Check the result The kube-system is patched successfully. Summary The tenant-owner can patch any arbitrary…

Published by the source

20 Aug 2024, 18:34 UTC

Last modified by the source

14 Aug 2025, 13:32 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mq69-4j5w-3qwp

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

# Patch Next advisory brief: CVE-2024-39690

Advisory: Capsule tenant owner with "patch namespace" permission can hijack system namespaces
IDs: CVE-2024-39690, GHSA-mq69-4j5w-3qwp
Record: https://patchnext.com/advisories/cve-2024-39690 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.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.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectcapsule/capsule: affected <= 0.7.0; fixed in 0.7.1

## 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://github.com/advisories/GHSA-mq69-4j5w-3qwp (GitHub-reviewed advisory GHSA-mq69-4j5w-3qwp lists affected ranges: Go github.com/projectcapsule/capsule >=0 <=0.7.0)

Commands are suggestions: review each one before running it.