# Gogs's write-level collaborators can mutate admin-only repository settings via API

Advisory record · `GHSA-268j-37xf-pp52`

- **Identifiers:** `GHSA-268j-37xf-pp52` · `CVE-2026-52808` · `GO-2026-5065`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 23 Jun 2026
- **Updated:** 21 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Jun 2026, 17:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gogs.io/gogs` (Go): affected `<0.14.3`; fixed in `0.14.3`

## Machine-written summary

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

> Gogs (gogs.io/gogs) versions before 0.14.3 let a user with write-level collaborator access to a repository change admin-only settings through three API endpoints: the issue tracker, wiki, and mirror sync. An attacker with that access can disable the native issue tracker or wiki, or point them to attacker-controlled external URLs that visitors would be sent to, and can trigger mirror syncs. Upgrade to Gogs 0.14.3 or later, which fixes the issue.

Written 6 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 41st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-268j-37xf-pp52)

## Sources

- [GitHub Advisory Database: GHSA-268j-37xf-pp52](https://github.com/advisories/GHSA-268j-37xf-pp52)
- [OSV: GHSA-268j-37xf-pp52](https://osv.dev/vulnerability/GHSA-268j-37xf-pp52)
- <https://github.com/gogs/gogs/security/advisories/GHSA-268j-37xf-pp52>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-52808>
- <https://github.com/gogs/gogs/pull/8327>
- <https://github.com/gogs/gogs/commit/6283462119bd8894f1599d70339b5e823f99954a>
- <https://github.com/gogs/gogs>
- <https://github.com/gogs/gogs/releases/tag/v0.14.3>

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-268j-37xf-pp52>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-268j-37xf-pp52/>. Everything for agents: <https://agentprime.io/llms.txt>.