Quick answers
- Is CVE-2026-32820 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32820 being exploited in the wild.
- How severe is CVE-2026-32820?
- High severity, with a CVSS score of 7.5, published 20 July 2026.
- Which products and versions are affected?
- dataCycle-Engine dataCycle-CORE <= 25.07.3.
- Is there a fix for CVE-2026-32820?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-32820 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32820?
- Check whether you run dataCycle-Engine dataCycle-CORE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability (CWE-22) exists in the documentation and static markdown rendering module of dataCycle-CORE. The application fails to properly sanitize path segments, relying solely on a Rails HTML sanitizer which does not filter directory traversal sequences like '../'. An unauthenticated remote attacker can exploit this by providing crafted path segments to the /docs/*path or static endpoints. This allows the attacker to traverse outside of the restricted directories and read arbitrary Markdown (.md) files located in the application or engine root. The issue is resolved in version 26.06.08.
Affected products
- datacycle-engine dataCycle-CORE <= 25.07.3
Timeline
- 2026-06-24: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: CVE published to NVD