CVE-2024-45042

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

Score 4.4 from GitHub Security Advisory (severity: MODERATE) published 2024-09-26. NVD baseline CVSS 4.4; 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-2888 (ENISA EUVD) · GHSA-wc43-73w7-x2f5 (GitHub Security Advisories)Source: ENISA EUVD

4.4EG
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.3%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Ory Kratos is an identity, user management and authentication system for cloud services. Prior to version 1.3.0, given a number of preconditions, the highest_available setting will incorrectly assume that the identity’s highest available AAL is aal1 even though it really is aal2. This means that the highest_available configuration will act as if the user has only one factor set up, for that particular user. This means that they can call the settings and whoami endpoint without a aal2 session, even though that should be disallowed. An attacker would need to steal or guess a valid login OTP of a user who has only OTP for login enabled and who has an incorrect available_aal value stored, to exploit this vulnerability. All other aspects of the session (e.g. the session’s aal) are not impacted by this issue. On the Ory Network, only 0.00066% of registered users were affected by this issue, and most of those users appeared to be test users. Their respective AAL values have since been updated and they are no longer vulnerable to this attack. Version 1.3.0 is not affected by this issue. As a workaround, those who require MFA should disable the passwordless code login method. If that is not possible, check the sessions aal to identify if the user has aal1 or aal2.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
25th
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 (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% 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

September 26, 2024

Last Modified

April 15, 2026

References (1)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/ory/kratos @ 1.3.0 (fixes <= 1.2.0)—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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/ory/kratos—
  • every version up to 1.3.0: fixed in 1.3.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/ory/kratos

Frequently asked(5)

What is CVE-2024-45042?
CVE-2024-45042 is a medium-severity vulnerability; its CVE record was published on September 26, 2024. Ory Kratos is an identity, user management and authentication system for cloud services. Prior to version 1.3.0, given a number of preconditions, the highest_available setting will incorrectly assume that the identity’s highest available AAL is aal1 even though it really is aal2. This means that…
When was the CVE record for CVE-2024-45042 published?
The CVE record for CVE-2024-45042 was published on September 26, 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-45042 actively exploited?
CVE-2024-45042 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-45042?
CVE-2024-45042 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2024-45042?
A fix for CVE-2024-45042 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-45042?

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

Book a Demo →Browse All CVEs