CVE-2025-3509: Pre-Receive Hook Remote Code Execution vulnerability was identified in GitHub Enterprise Server that allowing Privilege Escalation
Noroxi assessment
Priority: Monitor (action score 28/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: 1.3% (FIRST EPSS); higher than 71% 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 13.17.1, 3.13.16, 3.14.13.
Low priority for now. Upgrade to GitHub Enterprise Server 13.17.1, 3.13.16, 3.14.13 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 Remote Code Execution (RCE) vulnerability was identified in GitHub Enterprise Server that allowed attackers to execute arbitrary code by exploiting the pre-receive hook functionality, potentially leading to privilege escalation and system compromise. The vulnerability involves using dynamically allocated ports that become temporarily available, such as during a hot patch upgrade. This means the vulnerability is only exploitable during specific operational conditions, which limits the attack window. Exploitation required either site administrator permissions to enable and configure pre-receive hooks or a user with permissions to modify repositories containing pre-receive hooks where this functionality was already enabled. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18 and was fixed in versions 3.17.1, 3.16.4, 3.15.8, 3.14.13, 3.13.16. This vulnerability was reported via the GitHub Bug Bounty program.
- Published
- Apr 17, 2025
- Updated
- Jun 17, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-94
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_P
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/AU:N/R:U/V:C/RE:M/U:Amber
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 itNoroxi 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 helpAffected 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.13.0 and later · up to and including 3.13.15affected · semverfixed in 3.13.16
- 3.14.0 and later · up to and including 3.14.12affected · semverfixed in 3.14.13
- 3.15.0 and later · up to and including 3.15.7affected · semverfixed in 3.15.8
- 3.16.0 and later · up to and including 3.16.3affected · semverfixed in 3.16.4
- 13.17.0 and later · before 13.17.1affected · semverfixed in 3.17.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.13.16
- github enterprise server3.14.0 and later · before 3.14.13
- github enterprise server3.15.0 and later · before 3.15.8
- github enterprise server3.16.0 and later · before 3.16.4
- github enterprise server3.17.0 and later · before 3.17.1
Same product
github: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection61This week
- CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server55Plan
- CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server47Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-3124Apr 17, 2025 · Missing Authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized access to private repository names21Monitor
- ← EarlierCVE-2025-3246Apr 17, 2025 · Markdown math block sanitization bypass allows privilege escalation and unauthorized workflow triggers34Monitor
- Later →CVE-2025-6600Jul 1, 2025 · GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Search API25Monitor
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 | 13.17.1 | Vendor (CNA) |
| GitHub Enterprise Server | 3.13.16 | Vendor (CNA) |
| GitHub Enterprise Server | 3.14.13 | Vendor (CNA) |
| GitHub Enterprise Server | 3.15.8 | Vendor (CNA) |
| GitHub Enterprise Server | 3.16.4 | Vendor (CNA) |
| GitHub Enterprise Server | 3.17.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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- R31nfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-1000178 days apartCode Injection Vulnerability in GitHub Enterprise Server Allows Arbitrary Code Execution via Message Handling28Monitor
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.
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
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:M/U:Amber
nvd-secondary
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)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.