Medium severity · published Aug 12, 2022
CVE-2022-38183
In Gitea before 1.16.9, it was possible for users to add existing issues to projects
6.5
CVSS
0.9%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.9% · higher than 58% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
Gitea · Gitea
before 1.16.9 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-38183
CVE.org
https://www.cve.org/CVERecord?id=CVE-2022-38183
Release Notes
https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/
Broken Link
https://herolab.usd.de/security-advisories/usd-2022-0015/
Third Party Advisory
https://security.gentoo.org/glsa/202210-14
More from Gitea
9.8
CVE-2026-60004
Gitea Code Injection Vulnerability
9.8
CVE-2026-59774
Gitea Org-mode file disclosure and code execution
9.8
CVE-2026-73278
Gitea WebAuthn bypass during OAuth and OIDC sign-in
9.8
CVE-2026-94205
Gitea fork workflow approval bypass through maintainer-triggered events
9.8
CVE-2022-42968
Gitea before 1.17.3 does not sanitize and escape refs in the git backend