Fides is an open-source privacy engineering platform for managing the fulfillment of data privacy requests in a runtime environment, and the enforcement of privacy regulations in code. The Fides Privacy Center allows data subject users to submit privacy and consent requests to data controller users of the Fides web application. Privacy requests allow data subjects to submit a request to access all person data held by the data controller, or delete/erase it. Consent request allows data subject users to modify their privacy preferences for how the data controller uses their personal data e.g. data sales and sharing consent opt-in/opt-out. If subject_identity_verification_required in the [execution] section of fides.toml or the env var FIDES__EXECUTION__SUBJECT_IDENTITY_VERIFICATION_REQUIRED is set to True on the fides webserver backend, data subjects are sent a one-time code to their email address or phone number, depending on messaging configuration, and the one-time code must be entered in the Privacy Center UI by the data subject before the privacy or consent request is submitted. It was identified that the one-time code values for these requests were generated by the python random module, a cryptographically weak pseduo-random number generator (PNRG). If an attacker generates several hundred consecutive one-time codes, this vulnerability allows the attacker to predict all future one-time code values during the lifetime of the backend python process. There is no security impact on data access requests as the personal data download package is not shared in the Privacy Center itself. However, this vulnerability allows an attacker to (i) submit a verified data erasure request, resulting in deletion of data for the targeted user and (ii) submit a verified consent request, modifying a user's privacy preferences. The vulnerability has been patched in Fides version 2.24.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.
CVE-2023-48224
“—” beside the score: it is equal to NVD's CVSS score.
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 1.0% (62nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALmedium confidence
- EG Risk
- 56EG Risk 56/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.0% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.0%
- EPSS %ILE
- 62nd
- 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.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 15, 2023
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026PEP 506 – Adding A Secrets Module To The Standard Library | peps.python.org
https://peps.python.org/pep-0506/Cryptographically Weak Generation of One-Time Codes for Identity Verification · Advisory · ethyca/fides · GitHub
https://github.com/ethyca/fides/security/advisories/GHSA-82vr-5769-6358commit 685bae61c203 (ethyca/fides)
Fix landed in ethyca/fides commit 685bae61c203 — awaiting tagged release
https://github.com/ethyca/fides/commit/685bae61c203d29ed189f4b066a5223a9bb774c6Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ethyca-fides | 1.9.9 ... 2.9.2 (53 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 36× 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 92 of 203 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. 8 repeat rows among the latest 100 are merged into the row they repeat. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-23 01:12 UTCEG score recompute
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-21 23:32 UTCEG score recompute
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
- 2026-10-20 21:53 UTCEG score recompute
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-18 07:46 UTCEG score recompute
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-12 18:16 UTCEG score recompute
- 2026-10-12 16:54 UTCOSV refresh
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-11 21:42 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-08 17:06 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 67 moreShow fewer
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-30 16:33 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-22 16:58 UTCOSV refresh
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-21 20:31 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.0% · 61st percentile
- 2026-09-17 19:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-12 14:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-03 13:00 UTCOSV refresh
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-01 04:35 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-24 14:14 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-17 02:48 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-10 23:57 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-03 10:34 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-02 02:25 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-01 21:06 UTCOSV refresh
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 1.0% · 59th percentile
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:ethyca-fides
Frequently asked(5)
What is CVE-2023-48224?
When was the CVE record for CVE-2023-48224 published?
Is CVE-2023-48224 actively exploited?
What is the CVSS score of CVE-2023-48224?
How do I remediate CVE-2023-48224?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-48224
Is Your Infrastructure Affected by CVE-2023-48224?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.