CVE-2025-31990
Denial of Service via Missing Rate Limiting in HCL Velocity
Publication date: 2026-02-07
Last updated on: 2026-02-07
Assigner: HCL Software
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| hcl | velocity | 5.1.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs because rate limiting for certain API calls in HCL Velocity is not enforced. Without rate limiting, an attacker can send a large number of requests to the system in a short period of time.
As a result, the system's resources can become overwhelmed, making it unresponsive to legitimate users. This type of attack is known as a Denial of Service (DoS) attack.
The issue is addressed and fixed in version 5.1.7 of HCL Velocity.
How can this vulnerability impact me? :
This vulnerability can impact you by causing the HCL Velocity system to become unresponsive or unavailable due to resource exhaustion from a flood of malicious API requests.
Legitimate users may be unable to access the system or its services during such an attack, leading to potential disruption of business operations.
The impact is classified as high availability impact (CVSS score 6.8), meaning the confidentiality and integrity of data are not affected, but the system's availability is severely compromised.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade HCL Velocity to version 5.1.7 where the issue is fixed.