# CVE-2026-32823: dataCycle State-Changing GET Endpoints Enable CSRF

> Attackers can force logged-in users to modify application state or impersonate users via malicious GET requests due to missing CSRF protections.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026

## What is CVE-2026-32823?

CVE-2026-32823 is a medium-severity vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-32823?


## How do I fix CVE-2026-32823?

No fix has been published for CVE-2026-32823 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32823 being exploited?

There is no known exploitation of CVE-2026-32823 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32823 and fix it if it is affected.

What it is: CVE-2026-32823 is a medium-severity vulnerability in datacycle-engine dataCycle-CORE, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32823 in the wild and no public exploit code.

Affected product: datacycle-engine dataCycle-CORE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32823/ (Markdown: https://insights.sbomify.com/CVE-2026-32823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32823
- OSV: https://osv.dev/vulnerability/CVE-2026-32823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32823/
Summaries are generated and may contain mistakes; the official description above is the record.