# CVE-2022-38183: Gitea allowed assignment of private issues

> Attackers can assign private issues to projects without permission, exposing private issue titles in Gitea.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-gitea-2022-38183, GHSA-fhv8-m4j4-cww2, GO-2024-2769, UBUNTU-CVE-2022-38183

## What is CVE-2022-38183?

CVE-2022-38183 is a medium-severity missing authorization vulnerability in Gitea Gitea, published on 12 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-38183?

4 open source packages ship an affected version, including code.gitea.io/gitea and gitea. It affects 1 product.


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

Products: Gitea Gitea.

## How do I fix CVE-2022-38183?

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

## Is CVE-2022-38183 being exploited?

There is no known exploitation of CVE-2022-38183 in the wild and no public exploit code.

## Other vulnerabilities in Gitea Gitea

- [CVE-2026-60004](https://insights.sbomify.com/CVE-2026-60004/): Gitea Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-73278](https://insights.sbomify.com/CVE-2026-73278/): Gitea WebAuthn bypass during OAuth and OIDC sign-in (critical 9.8)
- [CVE-2026-94205](https://insights.sbomify.com/CVE-2026-94205/): Gitea fork workflow approval bypass through maintainer-triggered events (critical 9.8)
- [CVE-2022-42968](https://insights.sbomify.com/CVE-2022-42968/): Gitea vulnerable to Argument Injection (critical 9.8)
- [CVE-2021-45330](https://insights.sbomify.com/CVE-2021-45330/): Improper Privilege Management in Gitea (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38183 and fix it if it is affected.

What it is: CVE-2022-38183 is a medium-severity missing authorization vulnerability in Gitea Gitea, published on 12 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38183 in the wild and no public exploit code.

Affected packages and fixed versions:
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.16.9
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.16.9
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.16.9
- gitea (Bitnami): affected all versions; fixed in 1.16.9

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-2022-38183/ (Markdown: https://insights.sbomify.com/CVE-2022-38183/index.md)
```

## Sources

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

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