CVE-2022-2281 [Low] | Information Disclosure in Gitlab

An information disclosure vulnerability in GitLab EE affecting all versions from 12.5 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allows disclosure of release titles if group milestones are associated with any project releases.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-28	0.73%	0.85%	+0.12%
2	2026-06-15	0.21%	0.73%	+0.52%
3	2026-01-15	—	0.21%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-28

0.73%

0.85%

+0.12%

2026-06-15

0.21%

0.73%

+0.52%

2026-01-15

—

0.21%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.6	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. 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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.2	1.4	[email protected]
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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: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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.9	1.4	[email protected]
4.3	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:N/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:P) Partial confidentiality impact. Integrity impact (I:N) No 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.6

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.2

1.4

[email protected]

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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: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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.9

1.4

[email protected]

4.3

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:N/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:P): Partial confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:N): No availability impact.

8.6

2.9

[email protected]

OS Trackers for CVE-2022-2281

vendor	priority	summary	link
`debian`	unimportant	CVE-2022-2281 unimportant priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1.	https://security-tracker.debian.org/tracker/CVE-2022-2281
`ubuntu`	low	CVE-2022-2281 low priority: Ubuntu including 1 source packages (gitlab), 11 status rows across 11 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): DNE 9, ignored 1, needs-triage 1.	https://ubuntu.com/security/CVE-2022-2281

Affected software / configurations for CVE-2022-2281

Vendor	Product	Version	Raw CPE
gitlab	gitlab	>= 12.5.0, < 14.10.5	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	>= 15.0.0, < 15.0.4	cpe:2.3:a:gitlab:gitlab:::::enterprise:::*
gitlab	gitlab	15.1.0	cpe:2.3:a:gitlab:gitlab:15.1.0::::enterprise:::

References for CVE-2022-2281

URL	Tags
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-2281.json	Vendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/issues/271172	Broken Link
https://hackerone.com/reports/1012659	Permissions Required Third Party Advisory

URL

CVE-2022-2281

Exploit prediction scoring system (EPSS) score for CVE-2022-2281

Common vulnerability scoring system (CVSS) metrics for CVE-2022-2281

Weakness enumeration for CVE-2022-2281

OS Trackers for CVE-2022-2281

Affected software / configurations for CVE-2022-2281

References for CVE-2022-2281