NVD / CVE Program· CNA GitHub_P

CVE-2024-9487: An Improper Verification of Cryptographic Signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be…

CriticalCVSS 9.5 · v4.0—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 46/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 25.6% (FIRST EPSS); higher than 97.9% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: GitHub Enterprise Server 3.11.16, 3.12.10, 3.13.5.

Add it to your regular patch cycle. Upgrade to GitHub Enterprise Server 3.11.16, 3.12.10, 3.13.5 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

An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be bypassed resulting in unauthorized provisioning of users and access to the instance. Exploitation required the encrypted assertions feature to be enabled, and the attacker would require direct network access as well as a signed SAML response or metadata document. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.15 and was fixed in versions 3.11.16, 3.12.10, 3.13.5, and 3.14.2. This vulnerability was reported via the GitHub Bug Bounty program.

BDU:2024-08158

Published: Oct 10, 2024
Updated: Jun 17, 2026
EPSS: 25.6% · 97th percentile
CWE: CWE-347

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 38 / 40 · 9.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 8 / 30 · 25.6%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_P: 9.5; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/R:U/V:C/RE:M/U:Red

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
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi 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 help

Affected 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.11.0 and later · up to and including 3.11.15affected · semverfixed in 3.11.16
- 3.12.0 and later · up to and including 3.12.9affected · semverfixed in 3.12.10
- 3.13.0 and later · up to and including 3.13.4affected · semverfixed in 3.13.5
- 3.14.0 and later · up to and including 3.14.1affected · semverfixed in 3.14.2

Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

github enterprise serverbefore 3.11.16
github enterprise server3.12.0 and later · before 3.12.10
github enterprise server3.13.0 and later · before 3.13.5
github enterprise server3.14.0 and later · before 3.14.2

Same product

github: all records

Other highest-scoring records for the same primary product.

CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection
61This week
CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server
55Plan
CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server
47Plan

Published before and after this one in the same product

← EarlierCVE-2024-8263Sep 23, 2024 · An improper privilege management vulnerability allowed arbitrary workflows to be committed using an improperly scoped PAT through the use…
24Monitor
← EarlierCVE-2024-8770Sep 23, 2024 · A Cross-Site Scripting (XSS) vulnerability was identified in the repository transfer feature of GitHub Enterprise Server, which allows…
23Monitor
Later →CVE-2024-9539Oct 11, 2024 · An information disclosure vulnerability was identified in GitHub Enterprise Server via attacker uploaded asset URL allowing the attacker to…
22Monitor

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	3.11.16	Vendor (CNA)
GitHub Enterprise Server	3.12.10	Vendor (CNA)
GitHub Enterprise Server	3.13.5	Vendor (CNA)
GitHub Enterprise Server	3.14.2	Vendor (CNA)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2024-9487	—

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

SecureSAML.comfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-680051 days apartAn XML signature wrapping vulnerability was present in GitHub Enterprise Server (GHES) when using SAML authentication with specific…
38Monitor
CVE-2025-23369103 days apartImproper Verification of Cryptographic Signature in GitHub Enterprise Server Allows Signature Spoofing by Improper Validation
31Monitor

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: patch commit or PR link.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/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:X/R:U/V:C/RE:M/U:Red

nvd-secondary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const claims = jwt.verify(token, publicKey);

Fixed

1const claims = jwt.verify(token, publicKey, {
2  algorithms: ["RS256"],
3  issuer: "https://id.example.com",
4  audience: "portal",
5});

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)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

docs.github.com/en/enterprise-server@3.11/admin/release-notes#3.11.16

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records