NVD / CVE Program· CNA GitHub_P

CVE-2024-6800: An XML signature wrapping vulnerability was present in GitHub Enterprise Server (GHES) when using SAML authentication with specific identity

Noroxi assessment

Priority: Monitor (action score 38/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 74.7% 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.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: GitHub GitHub Enterprise Server 3.10.16, 3.11.14, 3.12.8.

Low priority for now. Upgrade to GitHub GitHub Enterprise Server 3.10.16, 3.11.14, 3.12.8 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 XML signature wrapping vulnerability was present in GitHub Enterprise Server (GHES) when using SAML authentication with specific identity providers utilizing publicly exposed signed federation metadata XML. This vulnerability allowed an attacker with direct network access to GitHub Enterprise Server to forge a SAML response to provision and/or gain access to a user with site administrator privileges. Exploitation of this vulnerability would allow unauthorized access to the instance without requiring prior authentication. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.13.3, 3.12.8, 3.11.14, and 3.10.16. This vulnerability was reported via the GitHub Bug Bounty program.

CriticalCVSS 9.5 · v4.0—No exploit Fix available

BDU:2024-07035

Published: Aug 20, 2024
Updated: Jun 17, 2026
EPSS: 1.5% · 74th percentile
CWE: CWE-347

Report tools

JSON

Action score

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation: none
Automatable: yes
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:H/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
No public exploit code on record
A fix has been released

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

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

github enterprise server3.10.0 and later · before 3.10.16
github enterprise server3.11.0 and later · before 3.11.14
github enterprise server3.12.0 and later · before 3.12.8
github enterprise server3.13.0 and later · before 3.13.3

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 GitHub Enterprise Server
- 3.13.0 and later · up to and including 3.13.2affected · semverfixed in 3.13.3
- 3.12.0 and later · up to and including 3.12.7affected · semverfixed in 3.12.8
- 3.11.0 and later · up to and including 3.11.13affected · semverfixed in 3.11.14
- 3.10.0 and later · up to and including 3.10.15affected · semverfixed in 3.10.16

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
46Plan

Published before and after this one in the same product

← EarlierCVE-2024-6395Jul 16, 2024 · GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Deploy Keys
25Monitor
← EarlierCVE-2024-6337Aug 20, 2024 · Incorrect Authorization allows read access to issues in GitHub Enterprise Server
23Monitor
Later →CVE-2024-7711Aug 20, 2024 · An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server, allowing an attacker to update the title, assignees, an
21Monitor

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 GitHub Enterprise Server	3.10.16	Vendor (CNA)
GitHub GitHub Enterprise Server	3.11.14	Vendor (CNA)
GitHub GitHub Enterprise Server	3.12.8	Vendor (CNA)
GitHub GitHub Enterprise Server	3.13.3	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

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

ahacker1finder

Variant candidates

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

CVE-2024-948751 days apartAn Improper Verification of Cryptographic Signature vulnerability was identified in GitHub Enterprise Server that allowed SAML SSO authentication to be bypassed
46Plan
CVE-2025-23369154 days apartImproper Verification of Cryptographic Signature in GitHub Enterprise Server Allows Signature Spoofing by Improper Validation
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

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:H/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

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.10/admin/release-notes#3.10.16

Show all references (3 more)

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

All records