Approved changes feed: RSS · Atom
cpe:2.3:a:gardener:gardener:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Gardener (3a4c55a2-a30f-5e54-a382-7fbacd125956) |
|---|---|
| Product | Gardener (d4b22278-dc74-59e2-acf9-b8a8e52f86a2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/gardener/gardener |
purl2cpe | 2026-06-01 10:14:06.636046 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-47284 |
vulnerable | 2026-06-08 07:27:09.894843 |
Gardener vulnerable to metadata injection for a project secret that can lead to privilege escalation
CRITICAL (9.9)
Gardener implements the automated management and operation of Kubernetes clusters as a service. A security vulnerability was discovered in the `gardenlet` component of Gardener prior to versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0. It could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster(s) where their shoot clusters are managed. This CVE affects all Gardener installations where gardener/gardener-extension-provider-gcp is in use. Versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 fix the issue.
Published: 2025-05-19T18:52:57.520Z
Updated: 2025-05-20T13:03:34.493Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-47283 |
vulnerable | 2026-06-08 07:27:09.894429 |
Bypassing project secret validation can lead to privilege escalation
CRITICAL (9.9)
Gardener implements the automated management and operation of Kubernetes clusters as a service. A security vulnerability was discovered in Gardener prior to versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 that could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster(s) where their shoot clusters are managed. This CVE affects all Gardener installations no matter of the public cloud provider(s) used for the seed clusters/shoot clusters. `gardener/gardener` (`gardenlet`) is the affected component. Versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 fix the issue.
Published: 2025-05-19T18:46:11.863Z
Updated: 2026-02-06T18:56:18.344Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-12494 |
vulnerable | 2026-06-08 05:12:39.241378 |
Details available
HIGH (8.5)
In Gardener before 0.20.0, incorrect access control in seed clusters allows information disclosure by sending HTTP GET requests from one's own shoot clusters to foreign shoot clusters. This occurs because traffic from shoot to seed via the VPN endpoint is not blocked.
Published: 2019-06-05T18:44:33.000Z
Updated: 2024-08-04T23:24:38.439Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-2475 |
vulnerable | 2026-06-08 05:11:37.225701 |
Details available
Following the Gardener architecture, the Kubernetes apiserver of a Gardener managed shoot cluster resides in the corresponding seed cluster. Due to missing network isolation a shoot's apiserver can access services/endpoints in the private network of its corresponding seed cluster. Combined with other minor Kubernetes security issues, the missing network isolation theoretically can lead to compromise other shoot or seed clusters in the "Gardener" context. The issue is rated high due to the high impact of a potential exploitation in "Gardener" context. This was fixed in Gardener release 0.12.4.
Published: 2018-10-09T13:00:00.000Z
Updated: 2024-08-05T04:21:33.648Z |
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.