How severe is CVE-2020-28991?

CVE-2020-28991 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-28991 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-28991?

CVE-2020-28991 affects Gitea. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-28991?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2020-28991 published?

CVE-2020-28991 was published on 2020-11-24 and last updated on 2026-06-17.

CVE-2020-28991

CVE-2020-28991 is a critical-severity vulnerability in Gitea with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gitea
Published: 2020-11-24
Last modified: 2026-06-17

Description

Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.

Frequently asked questions

What is CVE-2020-28991?: Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.
How severe is CVE-2020-28991?: CVE-2020-28991 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-28991 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-28991?: CVE-2020-28991 affects Gitea. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-28991?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-28991 published?: CVE-2020-28991 was published on 2020-11-24 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*

More vulnerabilities in Gitea

CVE-2022-42968 — Critical (CVSS 9.8): Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
CVE-2021-45331 — Critical (CVSS 9.8): An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges.…
CVE-2021-45330 — Critical (CVSS 9.8): An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies…
CVE-2021-45327 — Critical (CVSS 9.8): Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable…
CVE-2019-11576 — Critical (CVSS 9.8): Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known,…
CVE-2018-18926 — Critical (CVSS 9.8): Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs. This is related to…

All CVEs affecting Gitea →