Skip to content
Fencer Vulns
high 7.2

CVE-2020-14144 in the critical feed json

Arbitrary Code Execution in Gitea

published 2020-10-16 6 y ago modified 2026-09-08 2 mo ago also BIT-gitea-2020-14144 , EUVD-2024-1082 , GHSA-3h6c-c475-jm7v

cvss
7.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
95.4%
EPSS 95.4% chance of exploitation in 30 days, percentile 99.8%
public exploits
2
Metasploit, plus a Nuclei check

Summary

The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer environments where the documentation was not understood (e.g., one viewpoint is that the dangerousness of this feature should be documented immediately above the ENABLE_GIT_HOOKS line in the config file). NOTE: The vendor has indicated this is not a vulnerability and states "This is a functionality of the software that is limited to a very limited subset of accounts. If you give someone the privilege to execute arbitrary code on your server, they can execute arbitrary code on your server. We provide very clear warnings to users around this functionality and what it provides.

Patch / fix

  • go code.gitea.io/gitea 1.12.6
  • bitnami gitea 1.12.6

Timeline

  1. First public exploit (Metasploit exploit/multi/http/gitea_git_hooks_rce)
  2. Published

Exploit prediction

95.43% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
GitHub 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
OSV 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go code.gitea.io/gitea
>=1.1.0, <1.12.6
1.12.6
bitnami gitea
>=1.1.0, <1.12.6
1.12.6

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

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.