Gardener up to 1.142.5/1.143.2/1.144.1/1.144.99 customverbauthorizer mustCheckProjectMembers improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 1.08- |
Summary
A vulnerability was found in Gardener up to 1.142.5/1.143.2/1.144.1/1.144.99. It has been declared as problematic. The affected element is the function mustCheckProjectMembers of the component customverbauthorizer. Such manipulation leads to improper authorization.
This vulnerability is uniquely identified as CVE-2026-79767. The attack can be launched remotely. No exploit exists.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in Gardener up to 1.142.5/1.143.2/1.144.1/1.144.99 and classified as problematic. Affected by this issue is the function mustCheckProjectMembers of the component customverbauthorizer. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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 advisory is available at github.com. This vulnerability is handled as CVE-2026-79767 since 08/25/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1548.002 by the MITRE ATT&CK project.
Upgrading to version 1.142.6, 1.143.3, 1.144.2 or 1.145.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 1.142.0
- 1.142.1
- 1.142.2
- 1.142.3
- 1.142.4
- 1.142.5
- 1.143.0
- 1.143.1
- 1.143.2
- 1.144.0
- 1.144.1
- 1.144.2
- 1.144.3
- 1.144.4
- 1.144.5
- 1.144.6
- 1.144.7
- 1.144.8
- 1.144.9
- 1.144.10
- 1.144.11
- 1.144.12
- 1.144.13
- 1.144.14
- 1.144.15
- 1.144.16
- 1.144.17
- 1.144.18
- 1.144.19
- 1.144.20
- 1.144.21
- 1.144.22
- 1.144.23
- 1.144.24
- 1.144.25
- 1.144.26
- 1.144.27
- 1.144.28
- 1.144.29
- 1.144.30
- 1.144.31
- 1.144.32
- 1.144.33
- 1.144.34
- 1.144.35
- 1.144.36
- 1.144.37
- 1.144.38
- 1.144.39
- 1.144.40
- 1.144.41
- 1.144.42
- 1.144.43
- 1.144.44
- 1.144.45
- 1.144.46
- 1.144.47
- 1.144.48
- 1.144.49
- 1.144.50
- 1.144.51
- 1.144.52
- 1.144.53
- 1.144.54
- 1.144.55
- 1.144.56
- 1.144.57
- 1.144.58
- 1.144.59
- 1.144.60
- 1.144.61
- 1.144.62
- 1.144.63
- 1.144.64
- 1.144.65
- 1.144.66
- 1.144.67
- 1.144.68
- 1.144.69
- 1.144.70
- 1.144.71
- 1.144.72
- 1.144.73
- 1.144.74
- 1.144.75
- 1.144.76
- 1.144.77
- 1.144.78
- 1.144.79
- 1.144.80
- 1.144.81
- 1.144.82
- 1.144.83
- 1.144.84
- 1.144.85
- 1.144.86
- 1.144.87
- 1.144.88
- 1.144.89
- 1.144.90
- 1.144.91
- 1.144.92
- 1.144.93
- 1.144.94
- 1.144.95
- 1.144.96
- 1.144.97
- 1.144.98
- 1.144.99
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Gardener 1.142.6/1.143.3/1.144.2/1.145.0
Timeline
08/25/2026 CVE reserved09/22/2026 Advisory disclosed
09/22/2026 VulDB entry created
09/22/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-79767 (🔒)
GCVE (CVE): GCVE-0-2026-79767
GCVE (VulDB): GCVE-100-408722
Entry
Created: 09/22/2026 22:21Changes: 09/22/2026 22:21 (64)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.