CVE-2021-45327

Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API. which could let a remote malisious user execute arbitrary code.

Published: 2022-02-08 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-45327 is rated High Risk (66.5/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 2.06%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-45327

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 2.28% 2.06% -0.22%
2 2026-05-29 0.87% 2.28% +1.41%
3 2025-11-21 — 0.87% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-45327

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2021-45327

GitHub Security Advisory for CVE-2021-45327

OS Trackers for CVE-2021-45327

vendor priority summary link
alpine critical CVE-2021-45327: 1 source package rows (gitea); 11 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 4. https://security.alpinelinux.org/vuln/CVE-2021-45327
ubuntu medium CVE-2021-45327 medium priority: Ubuntu including 2 source packages (golang-code.gitea-git, golang-code.gitea-sdk), 28 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 12, ignored 8, needs-triage 8. https://ubuntu.com/security/CVE-2021-45327

Affected software / configurations for CVE-2021-45327

Vendor Product Version Raw CPE
gitea gitea < 1.11.2 cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*

References for CVE-2021-45327

URL Tags
https://blog.gitea.io/2020/03/gitea-1.11.2-is-released/ Release Notes Vendor Advisory
https://github.com/go-gitea/gitea/pull/10462 Patch Third Party Advisory
https://github.com/go-gitea/gitea/pull/10465 Patch Third Party Advisory
https://github.com/go-gitea/gitea/pull/10582 Patch Third Party Advisory
cvelogic Threat Intelligence