Approved changes feed: RSS · Atom
cpe:2.3:a:openkruise:kruise:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Openkruise (e4ab0750-cc10-5fa5-9ebc-a8a2fd11600b) |
|---|---|
| Product | Kruise (b636929c-44b5-5653-8e8f-6ce533b943b5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/openkruise/kruise |
purl2cpe | 2026-06-01 10:11:14.918755 |
pkg:golang/github.com/openkruise/kruise |
purl2cpe | 2026-06-01 10:11:14.918757 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-24005 |
vulnerable | 2026-06-08 07:51:16.516417 |
OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field
NONE
Kruise provides automated management of large-scale applications on Kubernetes. Prior to versions 1.8.3 and 1.7.5, PodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers. The webhook validation does not restrict the Host field in these probe configurations. Since kruise-daemon runs with hostNetwork=true, it executes probes from the node network namespace. An attacker with PodProbeMarker creation permission can specify arbitrary Host values to trigger SSRF from the node, perform port scanning, and receive response feedback through NodePodProbe status messages. Versions 1.8.3 and 1.7.5 patch the issue.
Published: 2026-02-25T18:53:30.170Z
Updated: 2026-02-26T20:44:09.282Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-30617 |
vulnerable | 2026-06-08 06:04:39.963318 |
Leverage the kruise-daemon pod to list all secrets in the entire cluster
MEDIUM (6.5)
Kruise provides automated management of large-scale applications on Kubernetes. Starting in version 0.8.0 and prior to versions 1.3.1, 1.4.1, and 1.5.2, an attacker who has gained 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, the attacker can leverage the "captured" secrets (e.g. the kruise-manager service account token) to gain extra privileges such as pod modification. Versions 1.3.1, 1.4.1, and 1.5.2 fix this issue. A workaround is available. For users that do not require imagepulljob functions, they can modify kruise-daemon-role to drop the cluster level secret get/list privilege.
Published: 2024-01-03T15:29:17.552Z
Updated: 2025-06-16T18:10:14.525Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.