NVD / CVE Program· CNA GitHub_P

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

MediumCVSS 5.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: GitHub Enterprise Server 3.4.18, 3.5.15, 3.6.11.
Severity is disputed: the assigning authority (CNA) scores it 7.7, NVD 5.3.

Low priority for now. Upgrade to GitHub Enterprise Server 3.4.18, 3.5.15, 3.6.11 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Auth bypass

Published: Apr 7, 2023
Updated: Jun 17, 2026
EPSS: 0.4% · 40th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.3
CNA · GitHub_P: 7.7; 2.4 point gap

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
github	enterprise server	cpe:2.3:a:github:enterprise_server

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.

GitHub Enterprise Server
- 3.9.0not affected
- 3.4.0 and later · up to and including 3.4.17affected · semverfixed in 3.4.18
- 3.5.0 and later · up to and including 3.5.14affected · semverfixed in 3.5.15
- 3.6.0 and later · up to and including 3.6.10affected · semverfixed in 3.6.11
- 3.7.0 and later · up to and including 3.7.7affected · semverfixed in 3.7.8
- 3.8.0 and later · before 3.8.1affected · semverfixed in 3.8.1

Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

github enterprise serverbefore 3.4.18
github enterprise server3.5.0 and later · before 3.5.15
github enterprise server3.6.0 and later · before 3.6.11
github enterprise server3.7.0 and later · before 3.7.8
github enterprise server3.8.0

Same product

github: all records

Other highest-scoring records for the same primary product.

CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection
61This week
CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server
55Plan
CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server
47Plan

Published before and after this one in the same product

← EarlierCVE-2022-46257Mar 7, 2023 · Information disclosure in GitHub Enterprise Server leading to unauthorized viewing of private repository names
17Monitor
← EarlierCVE-2023-23760Mar 8, 2023 · Path traversal in GitHub Enterprise Server leading to remote code execution
35Monitor
Later →CVE-2023-23762Apr 7, 2023 · Incorrect comparison vulnerability in GitHub Enterprise Server leading to commit smuggling
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
GitHub Enterprise Server	3.4.18	Vendor (CNA)
GitHub Enterprise Server	3.5.15	Vendor (CNA)
GitHub Enterprise Server	3.6.11	Vendor (CNA)
GitHub Enterprise Server	3.7.8	Vendor (CNA)
GitHub Enterprise Server	3.8.1	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2022-46256114 days apartPath traversal in GitHub Enterprise Server leading to remote code execution in GitHub Pages
36Monitor
CVE-2023-2376030 days apartPath traversal in GitHub Enterprise Server leading to remote code execution
35Monitor
CVE-2023-2238136 days apartCode injection in GitHub Enterprise Server leading to arbitrary environment variables in GitHub Actions
35Monitor
CVE-2023-2238050 days apartPath traversal in GitHub Enterprise Server leading to arbitrary file reading when building a GitHub Pages site
26Monitor

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

docs.github.com/en/enterprise-server@3.4/admin/release-notes#3.4.18

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records