# Gardener: Authorization Bypass via Group Subject Injection

Advisory record · `GHSA-gfjv-gqf2-c888`

- **Identifiers:** `GHSA-gfjv-gqf2-c888` · `CVE-2026-79767` · `GO-2026-6568`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 22 Sept 2026
- **Updated:** 4 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Sept 2026, 20:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/gardener/gardener` (Go): affected `<1.142.6 || >=1.143.0, <1.143.3 || >=1.144.0, <1.144.2`; fixed in `1.142.6`, `1.143.3`, `1.144.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Gardener's API server (github.com/gardener/gardener before 1.142.6, and gardener/gardener at 1.143.0 to before 1.143.3 or 1.144.0 to before 1.144.2) has an authorization bypass in the manage-members check. A project admin without manage-members permission can add Group or ServiceAccount subjects to a project's members, including system:authenticated, which grants all authenticated users full project access. Upgrade to 1.142.6, 1.143.3, or 1.144.2, depending on your release line.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 22 Sept 2026, 20:40 UTC: [Confirmed by GitHub Advisory Database](https://github.com/advisories/GHSA-gfjv-gqf2-c888)
- 31 Oct 2026, 14:12 UTC: First seen by agentprime
- 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gfjv-gqf2-c888)

## Sources

- [GitHub Advisory Database: GHSA-gfjv-gqf2-c888](https://github.com/advisories/GHSA-gfjv-gqf2-c888)
- [OSV: GHSA-gfjv-gqf2-c888](https://osv.dev/vulnerability/GHSA-gfjv-gqf2-c888)
- <https://github.com/gardener/gardener/security/advisories/GHSA-gfjv-gqf2-c888>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-79767>
- <https://github.com/gardener/gardener/pull/15080>
- <https://github.com/gardener/gardener/commit/63751db97dca6cc5ee5f966d4963415de6ae5545>
- <https://github.com/gardener/gardener>
- <https://github.com/gardener/gardener/releases/tag/v1.144.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gfjv-gqf2-c888>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gfjv-gqf2-c888/>. Everything for agents: <https://agentprime.io/llms.txt>.