Quick answers
- Is CVE-2026-32825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32825 being exploited in the wild.
- How severe is CVE-2026-32825?
- High severity, with a CVSS score of 7.3, published 20 July 2026.
- Which products and versions are affected?
- dataCycle-Engine dataCycle-CORE <= 25.07.3.
- Is there a fix for CVE-2026-32825?
- A patch was published on 2026-06-24: Fix released in version 26.06.08 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32825 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32825?
- 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
The dataCycle-CORE application fails to implement improper restriction of excessive authentication attempts (CWE-307). While the Ruby on Rails application utilizes the Devise authentication framework, the ':lockable' module is configured with both lock and unlock strategies explicitly disabled. Furthermore, no middleware or application-level request throttling is present. This vulnerability affects both the standard HTML login flow (/users/sign_in) and the JSON API endpoint (/api/v4/auth/login). The API endpoint is particularly vulnerable to automated exploitation as it does not require CSRF tokens. Successful exploitation allows an attacker to obtain valid session cookies or JSON Web Tokens (JWTs). The issue is addressed 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
- 2026-06-24: patched: Fix released in version 26.06.08