CVE-2023-23761 [High] | Authentication Bypass in Enterprise Server

An improper authentication vulnerability was identified in GitHub Enterprise Server that allowed an unauthorized actor to modify other users' secret gists by authenticating through an SSH certificate authority. To do so, a user had to know the secret gist's URL. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.9 and was fixed in versions 3.4.18, 3.5.15, 3.6.11, 3.7.8, and 3.8.1. This vulnerability was reported via the GitHub Bug Bounty program.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.12%	0.46%	+0.34%
2	2026-04-09	0.18%	0.12%	-0.06%
3	2026-04-08	—	0.18%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.12%

0.46%

+0.34%

2026-04-09

0.18%

0.12%

-0.06%

2026-04-08

—

0.18%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.7	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/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:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. 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:N) Service keeps running; no real outage angle.	1.3	5.8	[email protected]
5.3	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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: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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.6	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.7

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/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:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
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:N): Service keeps running; no real outage angle.

1.3

5.8

[email protected]

5.3

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/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: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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.6

3.6

[email protected]

Affected software / configurations for CVE-2023-23761

Vendor	Product	Version	Raw CPE
github	enterprise_server	< 3.4.18	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	>= 3.5.0, < 3.5.15	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	>= 3.6.0, < 3.6.11	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	>= 3.7.0, < 3.7.8	cpe:2.3:a:github:enterprise_server::::::::
github	enterprise_server	3.8.0	cpe:2.3:a:github:enterprise_server:3.8.0:::::::*

References for CVE-2023-23761

URL	Tags
https://docs.github.com/en/[email protected]/admin/release-notes#3.4.18	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.5.15	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.6.11	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.7.8	Release Notes
https://docs.github.com/en/[email protected]/admin/release-notes#3.8.1	Release Notes

URL

CVE-2023-23761 | Improper authentication vulnerability in GitHub Enterprise Server leading to modification of secret gists

Exploit prediction scoring system (EPSS) score for CVE-2023-23761

Common vulnerability scoring system (CVSS) metrics for CVE-2023-23761

Weakness enumeration for CVE-2023-23761

Affected software / configurations for CVE-2023-23761

References for CVE-2023-23761