CVE-2026-32823

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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, the application exposes server-side state changes through GET routes. Because browsers automatically send cookies on same-site top-level navigation and Rails does not apply CSRF protections to GET, an attacker can force a logged-in victim to modify application state by embedding a link, image, iframe, or redirect to one of these endpoints. This was confirmed on the target with a normal Standard account: a cross-site-style GET to watch_lists/:id/add_item?thing_id=... inserted content into a watch list with no CSRF token. Additional GET mutation routes exist in the codebase, including user impersonation for authorized admins and cache or translation state changes. This is patched in version 26.06.08.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 21, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
Patch available. Sources: github.
github Patch Available

State-Changing GET Endpoints Enable CSRF · Advisory · datacycle-engine/dataCycle-CORE · GitHub

https://github.com/datacycle-engine/dataCycle-CORE/security/advisories/GHSA-55wx-jh6w-jc57

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-01 16:44 UTCEG score recompute
  2. 2026-08-01 04:16 UTCEPSS rescore
  3. 2026-07-31 15:45 UTCEG score recompute
  4. 2026-07-30 16:28 UTCEPSS rescore
  5. 2026-07-30 14:44 UTCEG score recompute
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-29 13:46 UTCEG score recompute
  8. 2026-07-28 12:47 UTCEG score recompute
  9. 2026-07-27 14:13 UTCEPSS rescore
  10. 2026-07-27 11:46 UTCEG score recompute
  11. 2026-07-26 14:54 UTCEPSS rescore
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 10:47 UTCEG score recompute
  14. 2026-07-25 14:18 UTCEPSS rescore
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:17 UTCEPSS rescore
  17. 2026-07-24 14:17 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:09 UTCEG score recompute
  21. 2026-07-22 23:36 UTCEG score recompute
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:24 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 19:17 UTCEG score recompute
Show 3 more
  1. 2026-07-20 18:47 UTCEG score recompute
  2. 2026-07-20 16:38 UTCEG score recompute
  3. 2026-07-20 16:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32823?
CVE-2026-32823 is a medium vulnerability 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, the application exposes server-side state changes through GET routes.…
When was CVE-2026-32823 disclosed?
CVE-2026-32823 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32823 actively exploited?
CVE-2026-32823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-32823?
CVE-2026-32823 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-32823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32823, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-32823?

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

Start Free Scan →Browse All CVEs