Gardener Security Update Addresses 1 Vulnerability
Tech GuruQuick Answer
Gardener CVE-2026-79767 lets a project administrator who lacks manage-members permission bypass that check when changing Group members. A broad group grant can expose project resources, including secrets and cloud credentials, to unintended users. Apply the fix for the deployed branch and review existing project memberships; installing the patch alone does not revoke a grant already made.
Confirm Scope And Apply The Supported Fix
What to do now: inventory Gardener API server versions and Project member lists. Review unusually broad Group entries and limit project administration while upgrading. Preserve audit records before correcting unauthorized membership, and assess exposed credentials through the normal incident process.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | Gardener packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-gfjv-gqf2-c888 |
| CVE | CVE-2026-79767 |
| Authoritative release date | 2026-08-27 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-08-27 UTC (project advisory dates, not database ingestion) |
| Affected versions | github.com/gardener/gardener < 1.142.6; gardener/gardener >= 1.143.0, < 1.143.3; gardener/gardener >= 1.144.0, < 1.144.2 |
| Fixed version | Primary project fixes: 1.142.6, 1.143.3, 1.144.2 and 1.145.0. Select the supported branch applicable to the deployment. |
| CVSS base score | 5.5 (CVSS v3) |
| CVSS severity | Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The admission check compared human User subjects but failed to apply the documented membership permission to Group changes. The reported example broadens one project to all authenticated users. That is a project authorization failure; the actual reach depends on the added group, assigned role and resources in that project, rather than an automatic grant of cluster-wide administrator rights.
What To Validate Now
- Inventory. Record Gardener API server branch, project owners/admins, manage-members grants, Group memberships and audit coverage for Project changes.
- Establish applicability. Compare each deployment with the authority's affected-version statement: github.com/gardener/gardener < 1.142.6; gardener/gardener >= 1.143.0, < 1.143.3; gardener/gardener >= 1.144.0, < 1.144.2 Do not infer applicability from product family or severity alone.
- Remediate. Apply github.com/gardener/gardener 1.142.6; gardener/gardener 1.143.3; gardener/gardener 1.144.2 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. In an isolated test project with synthetic accounts, verify denial of Group membership changes by an admin lacking manage-members and successful changes by the authorized owner. Use a narrow test group, never a production-wide authenticated-user group.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
