NVD / CVE Program· CNA GitHub_P

CVE-2023-46645: Path traversal in GitHub Enterprise Server leading to arbitrary file reading when building a GitHub Pages site

Noroxi assessment

Priority: Monitor (action score 19/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.79% (FIRST EPSS); higher than 56.3% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: GitHub Enterprise Server 3.11.1, 3.7.19, 3.8.12.

Low priority for now. Upgrade to GitHub Enterprise Server 3.11.1, 3.7.19, 3.8.12 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

A path traversal vulnerability was identified in GitHub Enterprise Server that allowed arbitrary file reading when building a GitHub Pages site. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server since 3.7 and was fixed in version 3.7.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1. This vulnerability was reported via the GitHub Bug Bounty program.

MediumCVSS 4.9 · v3.1—No exploit Fix available

Path traversal

Published: Dec 21, 2023
Updated: Jun 17, 2026
EPSS: 0.7% · 56th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 19 / 40 · 4.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.9
CNA · GitHub_P: 6.8; 1.9 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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.

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

github enterprise server3.7.0 and later · before 3.7.19
github enterprise server3.8.0 and later · before 3.8.12
github enterprise server3.9.0 and later · before 3.9.7
github enterprise server3.10.0 and later · before 3.10.4

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.7.0 and later · before 3.7.19affected · semver
- 3.8.0 and later · before 3.8.12affected · semver
- 3.9.0 and later · before 3.9.7affected · semver
- 3.10.0 and later · before 3.8.4affected · semver
- 3.11.0 and later · before 3.11.1affected · semver

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
46Plan

Published before and after this one in the same product

← EarlierCVE-2023-23763Sep 1, 2023 · Information disclosure in GitHub Enterprise Server leading to private repository leakage
21Monitor
← EarlierCVE-2023-23766Sep 22, 2023 · Incorrect comparison vulnerability in GitHub Enterprise Server leading to commit smuggling
26Monitor
Later →CVE-2023-46646Dec 21, 2023 · Improper access control in all versions of GitHub Enterprise Server allows unauthorized users to view private repository names via the "Get
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.11.1	Vendor (CNA)
GitHub Enterprise Server	3.7.19	Vendor (CNA)
GitHub Enterprise Server	3.8.12	Vendor (CNA)
GitHub Enterprise Server	3.8.4	Vendor (CNA)
GitHub Enterprise Server	3.9.7	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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

yvvdwffinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2022-46255372 days apartImproper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE
39Monitor
CVE-2022-46256372 days apartPath traversal in GitHub Enterprise Server leading to remote code execution in GitHub Pages
36Monitor
CVE-2023-23760288 days apartPath traversal in GitHub Enterprise Server leading to remote code execution
35Monitor
CVE-2024-108254 days apartPath traversal vulnerability in GitHub Enterprise Server that allowed arbitrary file read with a specially crafted GitHub Pages artifact upload
26Monitor
CVE-2023-22380308 days apartPath traversal in GitHub Enterprise Server leading to arbitrary file reading when building a GitHub Pages site
26Monitor

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-2023-68470 days apartImproper Authentication in GitHub Enterprise Server leading to Authentication Bypass for Public Repository Data
30Monitor

Bug bounty scope

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

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

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

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

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

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

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

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.10/admin/release-notes#3.10.4

Show all references (4 more)

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

All records