NVD / CVE Program· CNA GitHub_P

CVE-2023-46647: Improper Privilege Management in GitHub Enterprise Server management console leads to privilege escalation

Noroxi assessment

Priority: Monitor (action score 35/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.63% (FIRST EPSS); higher than 50.6% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: GitHub Enterprise Server 3.10.3, 3.8.12, 3.9.6.

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

Improper privilege management in all versions of GitHub Enterprise Server allows users with authorized access to the management console with an editor role to escalate their privileges by making requests to the endpoint used for bootstrapping the instance. This vulnerability affected GitHub Enterprise Server version 3.8.0 and above and was fixed in version 3.8.12, 3.9.6, 3.10.3, and 3.11.0.

HighCVSS 8.8 · v3.1—No exploit Fix available

Published: Dec 21, 2023
Updated: Jun 17, 2026
EPSS: 0.6% · 50th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CNA vs NVD score

NVD: 8.8
CNA · GitHub_P: 8.0; 0.8 point gap

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

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.8.0 and later · before 3.8.12
github enterprise server3.9.0 and later · before 3.9.6
github enterprise server3.10.0 and later · before 3.10.3

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.11.0not affected
- 3.8.0 and later · up to and including 3.8.11affected · semverfixed in 3.8.12
- 3.9.0 and later · up to and including 3.9.5affected · semverfixed in 3.9.6
- 3.10.0 and later · up to and including 3.10.3affected · semverfixed in 3.10.3

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-46645Dec 21, 2023 · Path traversal in GitHub Enterprise Server leading to arbitrary file reading when building a GitHub Pages site
19Monitor
← EarlierCVE-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
Later →CVE-2023-46648Dec 21, 2023 · Insufficient Entropy in GitHub Enterprise Server Management Console Invitation Token
30Monitor

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.10.3	Vendor (CNA)
GitHub Enterprise Server	3.8.12	Vendor (CNA)
GitHub Enterprise Server	3.9.6	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.

Imre Radfinder

Variant candidates

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

CVE-2024-8810322 days apartPrivilege Management vulnerability was identified in GitHub Enterprise Server that allowed GitHub Apps to grant themselves write access
34Monitor
CVE-2024-3470120 days apartRepository administrator can bypass organization's ruleset using deploy keys
28Monitor
CVE-2024-190890 days apartImproper Privilege Management vulnerability was identified in GitHub Enterprise Server that allowed Privilege Escalation
26Monitor
CVE-2024-5566208 days apartImproper Privilege Management allows for access to unauthorized repository content during migration
26Monitor
CVE-2022-23737385 days apartImproper Privilege Management in GitHub Enterprise Server leading to page creation and deletion
26Monitor
CVE-2024-8263277 days apartAn improper privilege management vulnerability allowed arbitrary workflows to be committed using an improperly scoped PAT through the use of
24Monitor

Chain candidates

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

—

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.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

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

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

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

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

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

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

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

Abuse Elevation Control MechanismT1548

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 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.3

Show all references (3 more)

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

All records