CVE-2022-27313 json
Arbitrary file deletion in gitea
published 2022-05-03 4 y ago modified 2026-09-08 2 mo ago also BIT-gitea-2022-27313 , EUVD-2022-3917 , GHSA-g7p7-x6w7-w6qg , GO-2022-0442
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
Patch / fix
- go code.gitea.io/gitea 1.16.4
- bitnami gitea 1.16.4
- gitea Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 1.16.3-r0
alpine advisories ALPINE-CVE-2022-27313
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- github.com/go-gitea/gitea#19072 pull request
- github.com/go-gitea/gitea/releases/tag/v1.16.4 release
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.gitea.io/gitea | <1.16.4 |
1.16.4 |
| bitnami | gitea | >=1.16.3, <1.16.4 |
1.16.4 |
References
-
github.com
/go-gitea/gitea/pull/19072
web, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-27313
advisory, web
-
github.com
/go-gitea/gitea
package
-
github.com
/go-gitea/gitea/releases/tag/v1.16.4
web
-
github.com
/advisories/GHSA-g7p7-x6w7-w6qg
advisory
Sources
- CVE List CVE-2022-27313
- GitHub Advisory GHSA-g7p7-x6w7-w6qg
- NVD CVE-2022-27313
- OSV BIT-gitea-2022-27313
- OSV GO-2022-0442
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.