cve.bz

CVE-2025-23369 github enterprise server

7.6 highEPSS 2.1%Fix available

High (7.6) in github enterprise server. EPSS 2.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.6 high
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
2.1% (unchanged from 2.1% a week ago; 1.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-01-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • GitHub Enterprise Server: fixed in 3.12.14
  • GitHub Enterprise Server: fixed in 3.13.10
  • GitHub Enterprise Server: fixed in 3.14.7
  • GitHub Enterprise Server: fixed in 3.15.2

Ask an AI about this CVE

Show the promptExplain CVE-2025-23369 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-23369?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-23369?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-23369 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.12.0 through 3.12.13
GitHub Enterprise Serverfrom 3.13.0 through 3.13.9
GitHub Enterprise Serverfrom 3.14.0 through 3.14.6
GitHub Enterprise Serverfrom 3.15.0 through 3.15.1

Fixed in

ProductFixed in
GitHub Enterprise Server3.12.14
GitHub Enterprise Server3.13.10
GitHub Enterprise Server3.14.7
GitHub Enterprise Server3.15.2

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • hakivvi/CVE-2025-23369 Harbor Check: matches CVE 37 stars, created
    GitHub Entreprise Server SAML authentication bypass (CVE-2025-23369) exploit
  • Arian91/CVE-2025-23369_SAML_bypass Harbor Check: matches CVE 0 stars, created
    bypass SAML authentication on GitHub Enterprise

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON