dbcve.org
Enterprise ServerApplication · GitHub

CVE-2025-23369

HIGH · 8.8 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 3.12.14 / 3.13.10 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A cryptographic signature verification flaw in GitHub Enterprise Server's SAML single sign-on implementation allows authenticated internal users to spoof signatures, potentially enabling unauthorized access to other users' resources or privilege escalation. The vulnerability requires SAML SSO to be enabled and the attacker to already possess a valid user account.

MitigationUpgrade GitHub Enterprise Server to version 3.12.14, 3.13.10, 3.14.7, 3.15.2, or 3.16.0 or later. Instances not using SAML SSO are not affected by this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise ServerApplication
Affected:< 3.12.14>= 3.13.0, < 3.13.10>= 3.14.0, < 3.14.7>= 3.15.0, < 3.15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitHub Enterprise Server version
    Access the GitHub Enterprise Server Management Console. The version is displayed on the bottom of the left sidebar. Alternatively, run 'ghe-version' from the administrative SSH console.
    Affected if The installed version is less than 3.12.14, or between 3.13.0 and 3.13.9, or between 3.14.0 and 3.14.6, or between 3.15.0 and 3.15.1.
  2. Confirm SAML SSO is enabled
    In the Management Console, navigate to Authentication > SAML. Verify that SAML single sign-on is configured and enabled.
    Affected if SAML SSO is turned on and at least one identity provider is connected.
  3. Check for active SAML sessions
    Navigate to Site admin dashboard > Authentication > SAML sessions. Review the list of active SAML sessions to see which users are authenticating via SAML.
    Affected if There are users authenticating through SAML SSO, indicating the vulnerable code path is in use.
  4. Verify SAML signature validation settings
    In the Management Console under Authentication > SAML, examine the 'Signature method' and 'Digest method' settings. Check if 'Optional' signature verification is selected, which could indicate a misconfigured SAML setup.
    Affected if Signature verification is set to optional or weak cryptographic algorithms (such as SHA1) are in use for SAML signatures.

You are affected if your GitHub Enterprise Server version falls within the vulnerable ranges AND SAML SSO is enabled with users authenticating via SAML.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.12.14 / 3.13.10 / 3.14.7 or later
Fixed in 3.12.143.13.103.14.7
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.12.14, 3.13.10, 3.14.7, 3.15.2, or 3.16.0 or later. Instances not using SAML SSO are not affected by this vulnerability.

Recommended fix High confidence

3.16.0 (latest stable release that addresses all affected branches)

  1. Identify your current GitHub Enterprise Server version using the Management Console or administrative shell
  2. Backup all critical data and configurations before upgrading
  3. Plan upgrade based on your current version: if < 3.12.14 upgrade to 3.12.14 or later; if >= 3.13.0 and < 3.13.10 upgrade to 3.13.10 or later; if >= 3.14.0 and < 3.14.7 upgrade to 3.14.7 or later; if >= 3.15.0 and < 3.15.2 upgrade to 3.15.2 or later
  4. Download the appropriate upgrade package from GitHub Enterprise downloads
  5. Follow standard GitHub Enterprise Server upgrade procedures: stop services, apply upgrade, verify integrity, restart services
  6. After upgrade, verify the instance is functioning correctly and review audit logs
Caveat Standard GitHub Enterprise Server upgrade considerations apply; review release notes for your target version for any behavior changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23369 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data