{"items":[{"id":"NVI-00013052","kind":"vulnerability","title":"Gardener: Authorization Bypass via Group Subject Injection","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-gfjv-gqf2-c888","CVE-2026-79767"],"plain_summary":"GitHub lists this reviewed advisory for github.com/gardener/gardener, gardener/gardener, gardener/gardener. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-20c008866582e938f4f0c29ad1617be9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-22T20:40:43.000Z","value":"5.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4a81802b5fdd81357b6b2c157180e493"},{"kind":"CVSS","as_of":"2026-09-23T18:12:04.247Z","value":"5.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5628c7f87523ae360f48676b47551f2c"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.389%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.33022. Missing scores are unknown.","source_id":"sr-20c008866582e938f4f0c29ad1617be9"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4a81802b5fdd81357b6b2c157180e493","url":"https://github.com/advisories/GHSA-gfjv-gqf2-c888","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-gfjv-gqf2-c888","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:25:10.521Z"},{"id":"sr-5628c7f87523ae360f48676b47551f2c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-79767","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-79767","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:04.406Z"},{"id":"sr-20c008866582e938f4f0c29ad1617be9","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-79767","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.863Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"github.com/gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":["< 1.142.6"]},{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":[">= 1.143.0, < 1.143.3"]},{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":[">= 1.144.0, < 1.144.2"]}],"null_published_at":"2026-11-07T14:01:58.735Z","source_updated_at":"2026-09-22T20:40:43.000Z","source_disclosed_at":"2026-09-22T20:40:38.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T07:25:10.521Z"},{"id":"NVI-00013052","kind":"vulnerability","title":"Gardener: Authorization Bypass via Group Subject Injection","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-gfjv-gqf2-c888","CVE-2026-79767"],"plain_summary":"GitHub lists this reviewed advisory for github.com/gardener/gardener, gardener/gardener, gardener/gardener. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5628c7f87523ae360f48676b47551f2c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-22T20:40:43.000Z","value":"5.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4a81802b5fdd81357b6b2c157180e493"},{"kind":"CVSS","as_of":"2026-09-23T18:12:04.247Z","value":"5.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5628c7f87523ae360f48676b47551f2c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4a81802b5fdd81357b6b2c157180e493","url":"https://github.com/advisories/GHSA-gfjv-gqf2-c888","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-gfjv-gqf2-c888","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:25:10.521Z"},{"id":"sr-5628c7f87523ae360f48676b47551f2c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-79767","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-79767","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-04T09:59:04.406Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"github.com/gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":["< 1.142.6"]},{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":[">= 1.143.0, < 1.143.3"]},{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":[">= 1.144.0, < 1.144.2"]}],"null_published_at":"2026-11-05T19:10:23.274Z","source_updated_at":"2026-09-22T20:40:43.000Z","source_disclosed_at":"2026-09-22T20:40:38.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-11-01T07:25:10.521Z"},{"id":"NVI-00013052","kind":"vulnerability","title":"Gardener: Authorization Bypass via Group Subject Injection","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gfjv-gqf2-c888","CVE-2026-79767"],"plain_summary":"GitHub lists this reviewed advisory for github.com/gardener/gardener, gardener/gardener, gardener/gardener. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-22T20:40:43.000Z","value":"5.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-4a81802b5fdd81357b6b2c157180e493"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4a81802b5fdd81357b6b2c157180e493","url":"https://github.com/advisories/GHSA-gfjv-gqf2-c888","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-gfjv-gqf2-c888","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T07:25:10.521Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"github.com/gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":["< 1.142.6"]},{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":[">= 1.143.0, < 1.143.3"]},{"certainty":"source_listed","source_ids":["sr-4a81802b5fdd81357b6b2c157180e493"],"technology":"gardener/gardener","known_exclusions":[],"conditions_summary":"## Overview\nThe `manage-members` custom verb authorization check in the Gardener API server's `customverbauthorizer` admission plugin can be bypassed by adding `Group` or `ServiceAccount` subjects to a Project's member list. The check is documented as controlling \"human users or groups\", but the implementation only gates changes to `User`-kind subjects. A project admin (without `manage-members` permission) can add arbitrary Group subjects - including `system:authenticated` - granting all authenticated users full project-level access.\n## Technical Details\nThe official Gardener documentation at `docs/usage/project/projects.md:90-92` explicitly states:\n\n\nHowever, the `mustCheckProjectMembers()` function at `admission.go` compares old and new member lists using `findHumanUsersWithRoles()`, which only tracks subjects where `isHumanUser()` returns true:\n```go\nfunc mustCheckProjectMembers(oldMembers, members []core.ProjectMember, owner *rbacv1.Subject, userInfo user.Info) bool {\n    if apiequality.Semantic.DeepEqual(oldMembers, members) {\n        return false\n","public_affected_ranges":[">= 1.144.0, < 1.144.2"]}],"null_published_at":"2026-11-01T07:29:12.912Z","source_updated_at":"2026-09-22T20:40:43.000Z","source_disclosed_at":"2026-09-22T20:40:38.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T07:25:10.521Z"}],"next_cursor":null,"snapshot_revision":"42594"}