dataCycle is a data management system for centrally storing, managing, searching, finding, and distributing data. In…
Summary
Vulnerability reported (CVE-2026-32821). Confidential information can be exposed externally. Exploitable via user_email.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32821 has been found.
Attackers can target a specific entry point like user_email over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-32821" on the vendor's site.
CVE-2026-32821 — CWE-285 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: user_email / add_item / remove_item
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) has been reported. Attackers reach the vulnerable code path via user_email.
Check the vendor advisory for the affected versions. Attack surface: user_email / add_item / remove_item.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。