CVE-2024-52008

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-11-26) is not newer than that change (2025-09-23), so it does not.

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

Also known asEUVD-2024-3385 (ENISA EUVD) · GHSA-v7vm-rhmg-8j2r (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fides is an open-source privacy engineering platform. The user invite acceptance API endpoint lacks server-side password policy enforcement, allowing users to set arbitrarily weak passwords by bypassing client-side validation. While the UI enforces password complexity requirements, direct API calls can circumvent these checks, enabling the creation of accounts with passwords as short as a single character. When an email messaging provider is enabled and a new user account is created in the system, an invite email containing a special link is sent to the new user's email address. This link directs the new user to a page where they can set their initial password. While the user interface implements password complexity checks, these validations are only performed client-side. The underlying /api/v1/user/accept-invite API endpoint does not implement the same password policy validations. This vulnerability allows an invited user to set an extremely weak password for their own account during the initial account setup process. Therefore that specific user's account can be compromised easily by an attacker guessing or brute forcing the password. The vulnerability has been patched in Fides version 2.50.0. Users are advised to upgrade to this version or later to secure their systems against this threat. There are no known workarounds for this vulnerability.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 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
46th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
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 26, 2024

Last Modified

September 23, 2025

Advisory Details (1)

Auto-updated Aug 31, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Password Policy Bypass Vulnerability in Fides Webserver User Accept Invite API · Advisory · ethyca/fides · GitHub

https://github.com/ethyca/fides/security/advisories/GHSA-v7vm-rhmg-8j2r

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipethyca-fides @ 2.50.0 (fixes < 2.50.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)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ethyca-fides1.9.9 ... 2.9.2 (97 versions)
  • every version up to 2.50.0: fixed in 2.50.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-52008?
CVE-2024-52008 is a high-severity vulnerability; its CVE record was published on November 26, 2024. Fides is an open-source privacy engineering platform. The user invite acceptance API endpoint lacks server-side password policy enforcement, allowing users to set arbitrarily weak passwords by bypassing client-side validation. While the UI enforces password complexity requirements, direct API calls…
When was the CVE record for CVE-2024-52008 published?
The CVE record for CVE-2024-52008 was published on November 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 September 23, 2025; the record at its source may have been updated since.
Is CVE-2024-52008 actively exploited?
CVE-2024-52008 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-52008?
CVE-2024-52008 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-52008?
A fix for CVE-2024-52008 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-52008

Explore →

Is Your Infrastructure Affected by CVE-2024-52008?

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

Book a Demo →Browse All CVEs