Skip to main content
VulnerabilityPublished Updated

CVE-2025-31990: HCLSoftware HCL DevOps Velocity · Unthrottled Resource Allocation

Affects HCLSoftware HCL DevOps VelocitySource CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium : upgrade to 5.1.7 when convenient.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.1.7
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade HCL DevOps Velocity and com.hclsoftware/devops-velocity to 5.1.7.

Affected software

ProductAffectedFixed in
HCLSoftwareHCL DevOps VelocityAffected
  • <5.1.7
Fixed in
  • 5.1.7
Mavencom.hclsoftware/devops-velocitypkg:maven/com.hclsoftware/devops-velocityOther threatsAffected
  • <5.1.7
Fixed in
  • 5.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade HCL DevOps Velocity to version 5.1.7 or later, where the vulnerability has been addressed. Organizations should enforce strict access controls to limit high-privilege accounts and monitor their usage closely. Implementing additional API rate limiting and throttling at the network or application layer can provide defense-in-depth, reducing the risk of resource exhaustion. Continuous monitoring of API usage patterns and anomaly detection can help identify potential abuse early. Network-level protections such as Web Application Firewalls (WAFs) configured to detect and block excessive request rates can also be effective. Regularly auditing and reviewing API permissions and usage can minimize the attack surface. Finally, organizations should prepare incident response plans specific to DoS scenarios affecting DevOps infrastructure to ensure rapid recovery.

Description

Rate limiting for certain API calls is not being enforced, making HCL Velocity vulnerable to Denial of Service (DoS) attacks. An attacker could flood the system with a large number of requests, overwhelming its resources and causing it to become unresponsive to legitimate users. This vulnerability is fixed in 5.1.7.

References

Community reviews

Loading reviews…