CVE-2024-51744

LOWNVD 3.13.1
EchelonGraph scoreMEDIUM confidence

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

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2024-11-04. NVD baseline CVSS 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-3178 (ENISA EUVD) · GHSA-29wx-vh33-7x7r (GitHub Security Advisories)Source: ENISA EUVD

3.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 3.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in ParseWithClaims can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by ParseWithClaims return both error codes. If users only check for the jwt.ErrTokenExpired using error.Is, they will ignore the embedded jwt.ErrTokenSignatureInvalid and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the v5 branch to the v4 branch. In this logic, the ParseWithClaims function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/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)
Severity31% × 45%
Impact severity (EG Severity): CVSS 3.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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
0.6%
EPSS %ILE
47th
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 (3.1): severity, escalated by confirmed exploitation. This CVE's 3.1 is its impact severity (EG Severity), not escalated.

EG Severity
3.1 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

November 4, 2024

Last Modified

April 15, 2026

References (2)

Vendor Advisories for CVE-2024-51744(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhceph/grafana-rhel10:17713993312026-02-26redhat
redhatceph-2:18.2.1-381.el8cp2026-02-17redhat
redhatrhceph/grafana-rhel9:17706306072026-02-16redhat
redhatrhcos-416.94.202507222002-02025-07-30redhat
redhatopenshift4/ose-powervs-machine-controllers-rhel9:v4.15.0-202507111906.p0.g088808b.assembly.stream.el92025-07-23redhat
gogithub.com/golang-jwt/jwt/v4 @ 4.5.1 (fixes < 4.5.1)—ghsa

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-golang-jwt-jwt4.4.3-1 ... 5.0.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-golang-jwt-jwt—
  • every version up to 5.0.0+really4.5.2-1: fixed in 5.0.0+really4.5.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-golang-jwt-jwt—
  • every version up to 5.0.0+really4.5.2-1: fixed in 5.0.0+really4.5.2-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/golang-jwt/jwt/v4—
  • every version up to 4.5.1: fixed in 4.5.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 94 of 232 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-11-01 08:11 UTCEG score recompute
  3. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-29wx-vh33-7x7r · GitHub severity LOW · GitHub CVSS 3.1
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-25 16:58 UTCEG score recompute
  11. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-25 08:57 UTCEG score recompute
  13. 2026-10-25 08:57 UTCVendor advisory
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-18 06:53 UTCEG score recompute
  22. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 69 more
  1. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-12 17:40 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-11 21:06 UTCEG score recompute
  5. 2026-10-11 15:58 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-07 07:05 UTCOSV refresh
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-02 16:19 UTCEG score recompute
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-09-17 12:50 UTCOSV refresh
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  38. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  39. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  42. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  44. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  46. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  48. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  49. 2026-08-29 13:13 UTCOSV refresh
  50. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  52. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  53. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  54. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  55. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  56. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  57. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  58. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  59. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  60. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  61. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  62. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  63. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  64. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  65. 2026-08-13 01:00 UTCOSV refresh
  66. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  67. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  68. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  69. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Debian:12:golang-github-golang-jwt-jwt

Frequently asked(5)

What is CVE-2024-51744?
CVE-2024-51744 is a low-severity vulnerability; its CVE record was published on November 4, 2024. golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in ParseWithClaims can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by…
When was the CVE record for CVE-2024-51744 published?
The CVE record for CVE-2024-51744 was published on November 4, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-51744 actively exploited?
CVE-2024-51744 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-51744?
CVE-2024-51744 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2024-51744?
A fix for CVE-2024-51744 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-51744 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-51744

Explore →

Is Your Infrastructure Affected by CVE-2024-51744?

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

Book a Demo →Browse All CVEs