GitHub Enterprise Server
Improper Verification of Cryptographic Signature in GitHub Enterprise Server Allows Signature Spoofing by Improper Validation
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.12.0, <= 3.12.13
- >= 3.13.0, <= 3.13.9
- >= 3.14.0, <= 3.14.6
- >= 3.15.0, <= 3.15.1
Fixed in 3.12.14, 3.13.10, 3.14.7, 3.15.2, 3.16.0
Mitigation
Upgrade Enterprise Server to 3.12.14 or 3.13.10 or 3.14.7 or 3.15.2 or 3.16.0 or later.
Timeline
Days relative to CVE publicationFirst public PoC 18 days after publication; not in CISA KEV. First PoC: hakivvi/CVE-2025-23369 (created 8 Feb 2025, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| hakivvi/CVE-2025-23369 | 8 Feb 2025 +18 d | 37 | PoC |
| Arian91/CVE-2025-23369_SAML_bypass | 9 Feb 2025 +18 d | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.