CVE-2026-32821

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-45996 (ENISA EUVD)Source: ENISA EUVD

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

The CVE record names the fixed release — apply it.

dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, any authenticated API user who has their own access token can ask the collection API to evaluate permissions as a different user by supplying user_email. If the target user has collections, this can expose those collections through the API. In V4, once a collection id is known, the same controller also offers add_item and remove_item routes without any object-level authorize! checks, creating a likely cross-user modification path. This is patched in version 26.06.08.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
28th
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.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

July 20, 2026

Last Modified

October 24, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

API Collection Impersonation Via user_email And Missing Object- Level Authorization · Advisory · datacycle-engine/dataCycle-CORE · GitHub

https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-vjjr-9q8g-mgx7

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 96 of 154 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 58 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32821?
CVE-2026-32821 is a high-severity vulnerability; its CVE record was published on July 20, 2026. dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In dataCycle-CORE, the module handling core processing and framework rules, before and including version 25.07.3, any authenticated API user who has their own access token can ask the…
When was the CVE record for CVE-2026-32821 published?
The CVE record for CVE-2026-32821 was published on July 20, 2026. 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-32821 actively exploited?
CVE-2026-32821 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32821?
CVE-2026-32821 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-32821?
The CVE record for CVE-2026-32821 names the fix: "This is patched in version 26.06.08."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-32821

Explore →

Is Your Infrastructure Affected by CVE-2026-32821?

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

Book a Demo →Browse All CVEs