CVE-2024-37371

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2024-06-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2024-36619 (ENISA EUVD) · GHSA-8wpj-v5qv-3wf4 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.9%
EPSS %ILE
79th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 28, 2024

Last Modified

October 15, 2026

Advisory Details (5)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit.
GitHub commit

commit 55fbf435edbe (krb5/krb5)

Fix landed in krb5/krb5 commit 55fbf435edbe — awaiting tagged release

https://github.com/krb5/krb5/commit/55fbf435edbe2e92dd8101669b1ce7144bc96fef
Web page

Kerberos Security Advisories

https://web.mit.edu/kerberos/www/advisories/

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibkrb5support0 (1.13.2+dfsg-5ubuntu2.2+esm5) @ xenial2026-11-02ubuntu
redhatmysql-0:8.0.41-2.el9_52025-02-19redhat
redhatmysql:8.0-8100020250212154709.489197e62025-02-19redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.5.5-42024-12-16redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.4.7-32024-11-21redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.5.5-32024-09-30redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.4.7-22024-09-26redhat
redhatubi9/toolbox:9.4-12.17259068802024-09-11redhat
redhatkrb5-0:1.21.1-2.el9_42024-09-03redhat
redhatkrb5-0:1.17-19.el8_2.12024-08-27redhat
redhatkrb5-0:1.18.2-16.el8_6.12024-08-20redhat
redhatkrb5-0:1.19.1-16.el9_0.12024-08-20redhat
redhatkrb5-0:1.20.1-9.el9_2.12024-08-20redhat
redhatkrb5-0:1.18.2-29.el8_102024-08-13redhat
redhatkrb5-0:1.15.1-37.el7_7.42024-08-13redhat
redhatkrb5-0:1.15.1-55.el7_9.22024-08-07redhat
redhatkrb5-0:1.18.2-9.el8_4.12024-07-23redhat
redhatkrb5-0:1.18.2-26.el8_8.22024-07-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 12 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.2-r1: fixed in 1.20.2-r1
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.2-r1: fixed in 1.20.2-r1
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.3-r0: fixed in 1.20.3-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.3-r0: fixed in 1.20.3-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.3-r0: fixed in 1.20.3-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.3-r0: fixed in 1.20.3-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.3-r0: fixed in 1.20.3-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.20.3-r0: fixed in 1.20.3-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
krb51.18.3-6, 1.18.3-6+deb11u1, 1.18.3-6+deb11u2, 1.18.3-6+deb11u3, 1.18.3-6+deb11u4
  • every version up to 1.18.3-6+deb11u5: fixed in 1.18.3-6+deb11u5
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
krb51.20.1-2, 1.20.1-2+deb12u1
  • every version up to 1.20.1-2+deb12u2: fixed in 1.20.1-2+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.21.3-1: fixed in 1.21.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.21.3-1: fixed in 1.21.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 31× in last 7d / 107× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 306 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 206 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 17:35 UTCEG score recompute
  2. 2026-11-03 17:35 UTCVendor advisory
  3. 2026-11-03 17:35 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-03 16:42 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  5. 2026-11-02 19:33 UTCEG score recompute
  6. 2026-11-02 19:33 UTCVendor advisory
  7. 2026-11-02 19:33 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-02 16:41 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  9. 2026-11-01 21:31 UTCEG score recompute
  10. 2026-11-01 21:31 UTCVendor advisory
  11. 2026-11-01 21:30 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  13. 2026-10-31 23:29 UTCEG score recompute
  14. 2026-10-31 23:29 UTCVendor advisory
  15. 2026-10-31 23:29 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  17. 2026-10-31 01:27 UTCEG score recompute
  18. 2026-10-31 01:27 UTCVendor advisory
  19. 2026-10-31 01:27 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  21. 2026-10-30 03:25 UTCEG score recompute
  22. 2026-10-30 03:25 UTCVendor advisory
  23. 2026-10-30 03:25 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  25. 2026-10-29 05:24 UTCEG score recompute
Show 75 more
  1. 2026-10-29 05:24 UTCVendor advisory
  2. 2026-10-29 05:24 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  4. 2026-10-28 07:23 UTCEG score recompute
  5. 2026-10-28 07:23 UTCVendor advisory
  6. 2026-10-28 07:23 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  8. 2026-10-27 09:22 UTCEG score recompute
  9. 2026-10-27 09:22 UTCVendor advisory
  10. 2026-10-27 09:22 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  12. 2026-10-26 11:01 UTCVendor advisory
  13. 2026-10-26 11:01 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-25 17:08 UTCEG score recompute
  15. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  16. 2026-10-25 13:00 UTCEG score recompute
  17. 2026-10-25 13:00 UTCVendor advisory
  18. 2026-10-25 13:00 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  20. 2026-10-24 14:58 UTCVendor advisory
  21. 2026-10-24 14:58 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-23 16:57 UTCEG score recompute
  23. 2026-10-23 16:57 UTCVendor advisory
  24. 2026-10-23 16:57 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  26. 2026-10-22 18:55 UTCEG score recompute
  27. 2026-10-22 18:55 UTCVendor advisory
  28. 2026-10-22 18:55 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  29. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  30. 2026-10-21 20:53 UTCEG score recompute
  31. 2026-10-21 20:53 UTCVendor advisory
  32. 2026-10-21 20:52 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  33. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  34. 2026-10-20 22:51 UTCEG score recompute
  35. 2026-10-20 22:51 UTCVendor advisory
  36. 2026-10-20 22:51 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  38. 2026-10-20 00:24 UTCEG score recompute
  39. 2026-10-20 00:24 UTCVendor advisory
  40. 2026-10-20 00:24 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  41. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  42. 2026-10-18 23:15 UTCEG score recompute
  43. 2026-10-18 23:15 UTCVendor advisory
  44. 2026-10-18 23:15 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  45. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  46. 2026-10-18 07:11 UTCEG score recompute
  47. 2026-10-18 01:14 UTCEG score recompute
  48. 2026-10-18 01:14 UTCVendor advisory
  49. 2026-10-18 01:13 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  50. 2026-10-17 16:31 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  51. 2026-10-17 02:25 UTCEG score recompute
  52. 2026-10-17 02:25 UTCVendor advisory
  53. 2026-10-17 02:25 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  54. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  55. 2026-10-16 04:11 UTCEG score recompute
  56. 2026-10-16 04:11 UTCVendor advisory
  57. 2026-10-16 04:11 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  58. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  59. 2026-10-15 01:07 UTCEG score recompute
  60. 2026-10-15 01:07 UTCVendor advisory
  61. 2026-10-15 01:07 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  62. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  63. 2026-10-14 12:23 UTCEG score recompute
  64. 2026-10-14 12:23 UTCVendor advisory
  65. 2026-10-14 12:23 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  66. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  67. 2026-10-13 12:12 UTCVendor advisory
  68. 2026-10-13 12:12 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  69. 2026-10-12 17:51 UTCEG score recompute
  70. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  71. 2026-10-12 14:07 UTCVendor advisory
  72. 2026-10-12 14:07 UTCGHSA enrichmentGHSA-8wpj-v5qv-3wf4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  73. 2026-10-11 21:16 UTCEG score recompute
  74. 2026-10-11 16:09 UTCEG score recompute
  75. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.9% · 78th percentile

Frequently asked(5)

What is CVE-2024-37371?
CVE-2024-37371 is a critical-severity vulnerability; its CVE record was published on June 28, 2024. In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
When was the CVE record for CVE-2024-37371 published?
The CVE record for CVE-2024-37371 was published on June 28, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-37371 actively exploited?
CVE-2024-37371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-37371?
CVE-2024-37371 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2024-37371?
A fix for CVE-2024-37371 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-37371 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-37371

Explore →

Is Your Infrastructure Affected by CVE-2024-37371?

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