CVE-2025-23369 Security feature bypass in Enterprise Server
Unauthorized internal users can spoof cryptographic signatures in GitHub Enterprise Server when SAML SSO is not used.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-23369?
CVE-2025-23369 is a high-severity vulnerability in Github Enterprise Server, published on 21 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowed signature spoofing for unauthorized internal users. Instances not utilizing SAML single sign-on or where the attacker is not already an existing user were not impacted. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12.14, 3.13.10, 3.14.7, 3.15.2, and 3.16.0. This vulnerability was reported via the GitHub Bug Bounty program.
Weakness: CWE-347
Which versions are affected by CVE-2025-23369?
It affects 1 product.
Products include Github Enterprise Server.
How do I fix CVE-2025-23369?
No fix has been published for CVE-2025-23369 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-23369 being exploited?
There is no known exploitation of CVE-2025-23369 in the wild and no public exploit code.
Public exploit code: 2 proofs of concept on GitHub.
Other vulnerabilities in Github Enterprise Server
- CVE-2024-4985 Auth bypass in Enterprise Server
- CVE-2022-23739 Missing authorization in GitHub Enterprise Server
- CVE-2022-46255 Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE
- CVE-2021-22869 Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group
- CVE-2024-9487 Auth bypass in Enterprise Server
Sources
Also known as GHSA-jqqp-8w3h-pwg3.