Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.39% for the current model date.
BlackTreeCVE Intelligencegardener · gardener
Official source article: GitHub GHSA-GFJV-GQF2-C888 ↗. Check the applicable product and release in the original source.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gogardener/gardener | SEMVER: introduced 1.143.0; fixed 1.143.3 | 1.143.3 | OSV record ↗aggregator derived · 1 Oct 2026 |
| Gogardener/gardener | SEMVER: introduced 1.144.0; fixed 1.144.2 | 1.144.2 | OSV record ↗aggregator derived · 1 Oct 2026 |
| Gogithub.com/gardener/gardener | SEMVER: introduced 0; fixed 1.142.6 | 1.142.6 | OSV record ↗aggregator derived · 1 Oct 2026 |
| Gogithub.com/gardener/gardener | SEMVER: introduced 0 | Not stated | OSV record ↗aggregator derived · 1 Oct 2026 |
| Gogithub.com/gardener/gardener | SEMVER: introduced 0; fixed 1.142.6 | 1.142.6 | OSV record ↗aggregator derived · 1 Oct 2026 |
| gogardener/gardener | >= 1.143.0, < 1.143.3 | 1.143.3 | GitHub advisory ↗upstream repository advisory · 22 Sep 2026 |
| gogardener/gardener | >= 1.144.0, < 1.144.2 | 1.144.2 | GitHub advisory ↗upstream repository advisory · 22 Sep 2026 |
| gogithub.com/gardener/gardener | < 1.142.6 | 1.142.6 | GitHub advisory ↗upstream repository advisory · 22 Sep 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verifiedGardener implements the automated management and operation of Kubernetes clusters as a service. Prior to 1.142.6, 1.143.3, 1.144.2, and 1.145.0, the customverbauthorizer admission plugin's mustCheckProjectMembers manage-members check compares changes to User subjects but does not account for Group or ServiceAccount subjects in Project.spec.members. A project administrator who lacks manage-members permission can add arbitrary Group or ServiceAccount subjects, including the system:authenticated Group, and thereby grant broad project access. The resulting access can include Shoots, Secrets, and cloud provider credentials. This issue is fixed in versions 1.142.6, 1.143.3, 1.144.2, and 1.145.0.
Gardener implements the automated management and operation of Kubernetes clusters as a service. Prior to 1.142.6, 1.143.3, 1.144.2, and 1.145.0, the customverbauthorizer admission plugin's mustCheckProjectMembers manage-members check compares changes to User subjects but does not account for Group or ServiceAccount subjects in Project.spec.members. A project administrator who lacks manage-members permission can add arbitrary Group or ServiceAccount subjects, including the system:authenticated Group, and thereby grant broad project access. The resulting access can include Shoots, Secrets, and cloud provider credentials. This issue is fixed in versions 1.142.6, 1.143.3, 1.144.2, and 1.145.0.
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
Gardener implements the automated management and operation of Kubernetes clusters as a service. Prior to 1.142.6, 1.143.3, 1.144.2, and 1.145.0, the customverbauthorizer admission plugin's mustCheckProjectMembers manage-members check compares changes to User subjects but does not account for Group or ServiceAccount subjects in Project.spec.members. A project administrator who lacks manage-members permission can add arbitrary Group or ServiceAccount subjects, including the system:authenticated Group, and thereby grant broad project access. The resulting access can include Shoots, Secrets, and cloud provider credentials. This issue is fixed in versions 1.142.6, 1.143.3, 1.144.2, and 1.145.0.
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 22 Sept 2026 · Last source change 23 Sept 2026, 14:36 UTC · CWE-863 · Incorrect Authorization
Core structured fields are present and their contributing authorities are shown above.