CVE-2020-14144

CRITICALNVD 7.29.0▲
EchelonGraph scoreMEDIUM confidence

Score elevated to 9.0 because EPSS predicts 95% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.2 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 95%CVSS: 7.2Exploit: Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.2
EG Score
9.0CRITICALmedium confidence
EG Risk
83
EG Risk 83/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation95% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
95%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 16, 2020

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
code.gitea.io/gitea—
  • 1.1.0 up to 1.12.6: fixed in 1.12.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 1× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-08 16:38 UTCEPSS rescore
  2. 2026-09-30 20:40 UTCOSV refresh
  3. 2026-09-30 15:11 UTCEG score recompute
  4. 2026-09-22 14:43 UTCEPSS rescore
  5. 2026-09-21 20:28 UTCEPSS rescore
  6. 2026-09-18 19:23 UTCEPSS rescore
  7. 2026-09-12 02:53 UTCOSV refresh
  8. 2026-09-11 14:48 UTCEPSS rescore
  9. 2026-09-06 13:44 UTCEPSS rescore
  10. 2026-09-05 15:24 UTCEPSS rescore
  11. 2026-09-02 14:08 UTCEPSS rescore
  12. 2026-08-30 19:14 UTCEPSS rescore
  13. 2026-08-28 21:37 UTCEPSS rescore
  14. 2026-08-27 14:21 UTCEPSS rescore
  15. 2026-08-24 08:27 UTCOSV refresh
  16. 2026-08-19 17:00 UTCEPSS rescore
  17. 2026-08-16 02:11 UTCEPSS rescore
  18. 2026-08-13 21:57 UTCEPSS rescore
  19. 2026-08-08 04:49 UTCOSV refresh
  20. 2026-08-06 13:43 UTCEPSS rescore
  21. 2026-08-04 15:06 UTCEPSS rescore
  22. 2026-08-02 02:23 UTCEPSS rescore
  23. 2026-08-01 04:12 UTCEPSS rescore
  24. 2026-07-30 01:27 UTCEPSS rescore
  25. 2026-07-28 15:32 UTCEPSS rescore
Show 34 more
  1. 2026-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:49 UTCEG score recompute
  4. 2026-07-22 21:28 UTCEG score recompute▲ 1.80
  5. 2026-07-13 06:10 UTCEPSS rescore
  6. 2026-07-13 06:10 UTCEPSS rescore
  7. 2026-07-13 01:08 UTCOSV refresh
  8. 2026-07-07 13:43 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-07-01 15:03 UTCEPSS rescore
  13. 2026-06-24 10:20 UTCOSV refresh
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-17 17:50 UTCEPSS rescore
  17. 2026-06-17 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-15 17:46 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-08 14:15 UTCEPSS rescore
  24. 2026-06-08 14:15 UTCEPSS rescore
  25. 2026-06-07 15:00 UTCOSV refresh
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-05-31 22:29 UTCEPSS rescore
  29. 2026-05-31 22:29 UTCEPSS rescore
  30. 2026-05-29 13:42 UTCEPSS rescore
  31. 2026-05-29 13:42 UTCEPSS rescore
  32. 2026-05-26 13:42 UTCEPSS rescore
  33. 2026-05-26 13:42 UTCEPSS rescore
  34. 2026-05-23 06:41 UTCEG score recompute

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/multi/http/gitea_git_hooks_rce✓ verified
    First seen Oct 7, 2020

    Gitea Git Hooks Remote Code Execution

    Open source ↗
  • GitHub PoCp0dalirius/CVE-2020-14144-GiTea-git-hooks-rce
    First seen Mar 8, 2022

    A script to exploit CVE-2020-14144 - GiTea authenticated Remote Code Execution using git hooks

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-14144.yaml
    First seen Jan 1, 2020

    Gitea 1.1.0 - 1.12.5 - Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2020-14144?
CVE-2020-14144 is a critical vulnerability published on October 16, 2020. 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 ENABLEGITHOOKS line in…
When was CVE-2020-14144 disclosed?
CVE-2020-14144 was first published on October 16, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-14144 actively exploited?
CVE-2020-14144 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-14144?
CVE-2020-14144 has a CVSS v3 base score of 7.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2020-14144?
A fix for CVE-2020-14144 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-14144

Explore →

Is Your Infrastructure Affected by CVE-2020-14144?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.