CVE-2023-32321

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.7% (76th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

CKAN is an open-source data management system for powering data hubs and data portals. Multiple vulnerabilities have been discovered in Ckan which may lead to remote code execution. An arbitrary file write in resource_create and package_update actions, using the ResourceUploader object. Also reachable via package_create, package_revise, and package_patch via calls to package_update. Remote code execution via unsafe pickle loading, via Beaker's session store when configured to use the file session store backend. Potential DOS due to lack of a length check on the resource id. Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don't have access to it. Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don't have access to it. A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker's insecure pickle loading. All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1. Users are advised to upgrade. There are no known workarounds for these issues.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.7% × 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 total (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.7%
EPSS %ILE
76th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 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.7% 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: 3 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 total (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)3 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 total (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

May 26, 2023

Last Modified

November 21, 2024

Advisory Details (2)

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

Remote code execution and private information access via crafted resource ids · Advisory · ckan/ckan · GitHub

https://github.com/ckan/ckan/security/advisories/GHSA-446m-hmmm-hm8m
Web page

ckan/CHANGELOG.rst at 2a6080e61d5601fa0e2a0317afd6a8e9b7abf6dd · ckan/ckan · GitHub

https://github.com/ckan/ckan/blob/2a6080e61d5601fa0e2a0317afd6a8e9b7abf6dd/CHANGELOG.rst

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ckan0.11 ... 2.9.8 (104 versions)
  • every version up to 2.9.9: fixed in 2.9.9
  • 2.10.0 up to 2.10.1: fixed in 2.10.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 41× 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 210 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 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-32321?
CVE-2023-32321 is a critical-severity vulnerability; its CVE record was published on May 26, 2023. CKAN is an open-source data management system for powering data hubs and data portals. Multiple vulnerabilities have been discovered in Ckan which may lead to remote code execution. An arbitrary file write in resourcecreate and packageupdate actions, using the ResourceUploader object. Also…
When was the CVE record for CVE-2023-32321 published?
The CVE record for CVE-2023-32321 was published on May 26, 2023. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-32321 actively exploited?
CVE-2023-32321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-32321?
CVE-2023-32321 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-32321?
A fix for CVE-2023-32321 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-2023-32321

Explore →

Is Your Infrastructure Affected by CVE-2023-32321?

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

Book a Demo →Browse All CVEs