Unauthenticated Markdown file disclosure via path traversal
Published Jul 20, 2026 · Updated Jul 20, 2026
Path traversal in dataCycle CORE 25.07.3 and earlier allows remote attackers to read Markdown files through public rendering routes. The documentation and static Markdown renderer sanitizes attacker-controlled path segments as HTML instead of constraining the resolved path to its docs or static root. No authentication or user interaction is required, and disclosure is limited to reachable .md files under the application or engine root.
Summary
What happened
Path traversal in dataCycle CORE 25.07.3 and earlier allows remote attackers to read Markdown files through public rendering routes. The documentation and static Markdown renderer sanitizes attacker-controlled path segments as HTML instead of constraining the resolved path to its docs or static root. No authentication or user interaction is required, and disclosure is limited to reachable .md files under the application or engine root.
The record
- CVE
- CVE-2026-32820
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- dataCycle GmbH
- Product
- dataCycle CORE
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 25.07.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo