# CVE-2026-52800: Gogs: CSRF Leading to Organization Owner Takeover

> Attackers can trick organization owners into visiting crafted links to gain owner-equivalent privileges via CSRF in team management.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-pwx3-qcgw-vh7h, GO-2026-5556

## What is CVE-2026-52800?

CVE-2026-52800 is a high-severity vulnerability in gogs, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Gogs is an open source self-hosted Git service. Prior to 0.14.3, organization team member management can be performed via GET requests without CSRF protection. If a victim who is an organization owner is logged in and is tricked into visiting a crafted link, an attacker-controlled user can be added to the Owners team. As a result, the attacker gains organization owner–equivalent privileges. This vulnerability is fixed in 0.14.3.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-52800?

3 open source packages ship an affected version, including gogs.io/gogs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gogs.io/gogs` | Go | All versions | None |
| `gogs.io/gogs` | Go | All versions | 0.14.3 |
| `gogs.io/gogs` | Go | All versions | 0.14.3 |

## How do I fix CVE-2026-52800?

Upgrade gogs.io/gogs to 0.14.3 or later.

## Is CVE-2026-52800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52800 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-52800 and fix it if it is affected.

What it is: CVE-2026-52800 is a high-severity vulnerability in gogs, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52800 exists.

Affected packages and fixed versions:
- gogs.io/gogs (Go): affected all versions; no fix listed
- gogs.io/gogs (Go): affected all versions; fixed in 0.14.3
- gogs.io/gogs (Go): affected all versions; fixed in 0.14.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-52800/ (Markdown: https://insights.sbomify.com/CVE-2026-52800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-52800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-52800
- OSV: https://osv.dev/vulnerability/CVE-2026-52800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-52800/
Summaries are generated and may contain mistakes; the official description above is the record.