Kruise allows leveraging the kruise-daemon pod to list all secrets in the entire cluster

Exploitation

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

CVSS

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

EPSS

• CVE-2023-30617: 0.49% estimated exploitation activity in the next 30 days; percentile 42.12 (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.

Impact Attacker that has gain root privilege of the node that kruise-daemon run , can leverage the kruise-daemon pod to list all secrets in the entire cluster. After that, attackers can leverage the "captured" secrets (e.g. the kruise-manager service account token) to gain extra privilege such as pod modification. Workarounds For users that do not require imagepulljob functions, they can modify kruise-daemon-role to drop the cluster level secret get/list privilege Patches For users who're using v0.8.x ~ v1.2.x, please update the v1.3.1 For users who're using v1.3, please update the v1.3.1 For users who're using v1.4, please update the v1.4.1 For users who're using v1.5, please update the v1.5.2 References None

Published by the source

5 Jan 2024, 16:01 UTC

Last modified by the source

5 Jan 2024, 16:01 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-437m-7hj5-9mpw

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

# Patch Next advisory brief: CVE-2023-30617

Advisory: Kruise allows leveraging the kruise-daemon pod to list all secrets in the entire cluster
IDs: CVE-2023-30617, GHSA-437m-7hj5-9mpw
Record: https://patchnext.com/advisories/cve-2023-30617 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openkruise/kruise 1.5.2, 1.4.1, 1.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openkruise/kruise: affected >= 0.8.0, < 1.3.1; >= 1.4.0, < 1.4.1; >= 1.5.0, < 1.5.2; fixed in 1.4.1, 1.5.2, 1.3.1

## Suggested inspection (read-only)
- Go github.com/openkruise/kruise: 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/openkruise/kruise.
- 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-437m-7hj5-9mpw (GitHub-reviewed advisory GHSA-437m-7hj5-9mpw lists affected ranges: Go github.com/openkruise/kruise >=0.8.0 =1.4.0 =1.5.0 <1.5.2)

Commands are suggestions: review each one before running it.