CVE-2024-0200

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2024-01-16. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.2
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 72%
CISA-KEV: Not listedEPSS: 72%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. This vulnerability could lead to the execution of user-controlled methods and remote code execution. To exploit this bug, an actor would need to be logged into an account on the GHES instance with the organization owner role. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.12 and was fixed in versions 3.8.13, 3.9.8, 3.10.5, and 3.11.3. This vulnerability was reported via the GitHub Bug Bounty program.

CVSS v3
7.2
EG Score
7.2(medium)
EPSS
99.4%
KEV
Not listed

Published

January 16, 2024

Last Modified

November 21, 2024

References (8)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-16 17:01 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-15 01:59 UTCEPSS rescore
  10. 2026-07-15 01:59 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-12 05:45 UTCEPSS rescore
  13. 2026-07-12 05:45 UTCEPSS rescore
  14. 2026-07-09 19:08 UTCEPSS rescore
  15. 2026-07-08 15:13 UTCEPSS rescore
  16. 2026-07-04 06:29 UTCEPSS rescore
  17. 2026-07-01 15:05 UTCEPSS rescore
  18. 2026-06-30 23:21 UTCEPSS rescore
  19. 2026-06-30 23:21 UTCEPSS rescore
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 30 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-21 01:58 UTCEPSS rescore
  3. 2026-06-21 01:58 UTCEPSS rescore
  4. 2026-06-18 17:51 UTCEPSS rescore
  5. 2026-06-17 17:51 UTCEPSS rescore
  6. 2026-06-16 17:51 UTCEPSS rescore
  7. 2026-06-16 17:51 UTCEPSS rescore
  8. 2026-06-15 17:47 UTCEPSS rescore
  9. 2026-06-14 23:16 UTCEPSS rescore
  10. 2026-06-13 22:59 UTCEPSS rescore
  11. 2026-06-13 22:59 UTCEPSS rescore
  12. 2026-06-12 23:11 UTCEPSS rescore
  13. 2026-06-11 13:59 UTCEPSS rescore
  14. 2026-06-10 22:17 UTCEPSS rescore
  15. 2026-06-05 22:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 06:09 UTCEPSS rescore
  18. 2026-06-05 06:09 UTCEPSS rescore
  19. 2026-06-04 13:11 UTCEPSS rescore
  20. 2026-06-04 13:11 UTCEPSS rescore
  21. 2026-06-01 13:51 UTCEPSS rescore
  22. 2026-05-29 13:43 UTCEPSS rescore
  23. 2026-05-27 13:40 UTCEPSS rescore
  24. 2026-05-27 13:39 UTCEPSS rescore
  25. 2026-05-26 13:43 UTCEPSS rescore
  26. 2026-05-26 13:43 UTCEPSS rescore
  27. 2026-05-26 07:18 UTCEPSS rescore
  28. 2026-05-26 07:18 UTCEPSS rescore
  29. 2026-05-24 10:10 UTCEG score recompute
  30. 2026-05-24 10:10 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2024/CVE-2024-0200.yaml
    First seen Jan 1, 2024

    Github Enterprise Authenticated Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2024-0200?
CVE-2024-0200 is a high vulnerability published on January 16, 2024. An unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. This vulnerability could lead to the execution of user-controlled methods and remote code execution. To exploit this bug, an actor would need to be logged into an account on the…
When was CVE-2024-0200 disclosed?
CVE-2024-0200 was first published in the National Vulnerability Database on January 16, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-0200 actively exploited?
CVE-2024-0200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-0200?
CVE-2024-0200 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2024-0200?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-0200, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-0200

Explore →

Is Your Infrastructure Affected by CVE-2024-0200?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs