CVE-2021-22202 [Low] | CSRF in Gitlab

CVE-2021-22202 is rated Low Risk (23/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.48%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.16%	0.48%	+0.32%
2	2025-11-21	0.06%	0.16%	+0.10%
3	2025-11-18	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.16%

0.48%

+0.32%

2025-11-21

0.06%

0.16%

+0.10%

2025-11-18

—

0.06%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.4	3.1	LOW	`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N` 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:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	0.9	1.4	[email protected]
4.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N` 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:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.8	1.4	[email protected]
4.3	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:N/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	8.6	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

2.4

3.1

LOW

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N 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:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

0.9

1.4

[email protected]

4.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N 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:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.8

1.4

[email protected]

4.3

2.0

MEDIUM

AV:N/AC:M/Au:N/C:N/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

8.6

2.9

[email protected]

OS Trackers for CVE-2021-22202

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2021-22202 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1.	https://security-tracker.debian.org/tracker/CVE-2021-22202
`ubuntu`	medium	CVE-2021-22202 medium priority: Ubuntu including 1 source packages (gitlab), 13 status rows across 13 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): DNE 11, ignored 1, needs-triage 1.	https://ubuntu.com/security/CVE-2021-22202

Affected software / configurations for CVE-2021-22202

Vendor	Product	Version	Raw CPE
gitlab	gitlab	<= 13.10.0	cpe:2.3:a:gitlab:gitlab:::::community:::*
gitlab	gitlab	<= 13.10.0	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*

References for CVE-2021-22202

URL	Tags
https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22202.json	Vendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/issues/26017	Broken Link
https://hackerone.com/reports/471274	Permissions Required Third Party Advisory

URL

CVE-2021-22202

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

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

Weakness enumeration for CVE-2021-22202

OS Trackers for CVE-2021-22202

Affected software / configurations for CVE-2021-22202

References for CVE-2021-22202