# CVE-2026-58424: Permanent Fork PR Workflow Approval Gate Bypass

> Attackers can bypass approval gates for permanent fork pull requests, allowing unauthorized code changes in Gitea Git servers.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-777r-4v59-6486, GO-2026-6044

## What is CVE-2026-58424?

CVE-2026-58424 is a high-severity missing authorization vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Permanent Fork PR Workflow Approval Gate Bypass

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |

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

Upgrade code.gitea.io/gitea to 1.26.3 or later.

## Is CVE-2026-58424 being exploited?

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

Public exploit code:

- A flaw in Gitea Open Source Git Server’s approval‑gate logic allows a pull request that originates from a permanent fork to merge without satisfying the repository’s configured approval gates.  (github_poc): https://github.com/BridgerAlderson/CVE-2026-58424

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58424 is a high-severity missing authorization vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. Any signed-in user can exploit it over the network, 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-58424 exists.

Affected packages and fixed versions:
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.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-58424/ (Markdown: https://insights.sbomify.com/CVE-2026-58424/index.md)
```

## Sources

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

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