Quick answers
- Is CVE-2026-32806 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32806 being exploited in the wild.
- How severe is CVE-2026-32806?
- 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 (NVD); <= 26.06.11 (GitHub).
- Is there a fix for CVE-2026-32806?
- 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-32806 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32806?
- 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
An authorization bypass exists in dataCycle-CORE's /remote_render endpoint due to improper validation of requested partials. The endpoint fails to restrict which view partials can be rendered and does not apply controller-specific authorization checks before rendering. An authenticated attacker with low privileges can exploit this to request arbitrary partials or helper-backed render functions, effectively bypassing navigation and route-based access controls. This allows for the retrieval of server-side rendered admin content, such as PostgreSQL dashboard statistics and internal table names. The vulnerability is addressed in version 26.07.01 (or 26.06.08 depending on the source).
Affected products
- datacycle-engine dataCycle-CORE <= 25.07.3 (NVD); <= 26.06.11 (GitHub)
Timeline
- 2026-06-24: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: NVD publication date