Quick answers
- Is CVE-2025-31991 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-31991 being exploited in the wild.
- How severe is CVE-2025-31991?
- Medium severity, with a CVSS score of 6.8, published 13 April 2026.
- Which products and versions are affected?
- HCL Software DevOps Velocity versions prior to 5.1.7.
- Is there a fix for CVE-2025-31991?
- A patch was published on 2026-04-13: Fixed in version 5.1.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-31991 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-31991?
- Check whether you run Hcltech Devops Velocity. 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
HCL DevOps Velocity fails to properly enforce rate limiting on its authentication endpoint (CWE-307). The vulnerability allows a remote attacker to perform brute-force attacks against user accounts because the system does not effectively restrict excessive unsuccessful login attempts. While the vendor-provided CVSS vector suggests high privileges might be required for certain impacts, the nature of a brute-force vulnerability typically involves an unauthenticated or low-privileged network-based attacker attempting to escalate access. The issue is resolved in HCL DevOps Velocity version 5.1.7.
Affected products
- HCL Software DevOps Velocity versions prior to 5.1.7
Timeline
- 2026-04-13: disclosed
- 2026-04-13: advisory
- 2026-04-13: patched: Fixed in version 5.1.7