dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-31990

MEDIUM · 6.8 CVSS v3.1 Published 2026-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HCL Velocity fails to enforce rate limiting on certain API endpoints, allowing attackers to flood the system with excessive requests and exhaust server resources, leading to denial of service for legitimate users.

MitigationUpgrade HCL Velocity to version 5.1.7 or later, which includes the rate limiting fix for the affected API calls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate HCL Velocity installation
    Identify where HCL Velocity is installed; common locations include /opt/hcl/velocity, /app/hcl/velocity, or C:\Program Files\HCL\Velocity on Windows. Check for velocity.sh or velocity.bat startup scripts, or look for velocity.war in application servers.
    Affected if Cannot locate version information or installation directory is missing expected Velocity components
  2. Determine installed version number
    Check the product UI under Help > About, or inspect version files in the installation directory. Common locations include version.properties, VERSION.txt, or the velocity.war/META-INF/MANIFEST.MF file. The version is also often logged at application startup.
    Affected if Version cannot be determined or no version file exists in the installation
  3. Compare version to fixed release
    If version is found, compare it to 5.1.7. Versions before 5.1.7 (such as 5.1.0, 5.0.x, 4.x.x) are affected. The version string typically follows format like 5.1.6, 5.1.5, etc.
    Affected if Installed version is below 5.1.7 (for example, 5.1.6, 5.1.0, 5.0.1, 4.2.0)
  4. Identify exposed API endpoints
    Review network configuration and API gateway settings to determine which REST endpoints are externally accessible. Check velocity-server.conf or similar configuration files for exposed API paths. Common endpoints follow patterns like /api/v1/*, /velocity/api/*, or /services/*
    Affected if API endpoints are accessible from untrusted networks without authentication or rate limiting configured

Environment is affected if HCL Velocity version is below 5.1.7 AND the API endpoints are exposed to network traffic, as this combination allows the unpatched rate limiting vulnerability to be exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HCL Velocity to version 5.1.7 or later, which includes the rate limiting fix for the affected API calls.

Recommended fix Moderate confidence

5.1.7

  1. Back up the current HCL Velocity installation, configuration files, and database before starting the upgrade
  2. Download HCL Velocity version 5.1.7 from the official HCL support portal at support.hcl-software.com
  3. Stop the HCL Velocity service to ensure a clean upgrade process
  4. Install or apply version 5.1.7 following HCL's official upgrade documentation for your deployment method
  5. Verify the installation was successful by checking that all components started without errors
  6. Start or restart the HCL Velocity service
  7. Confirm that rate limiting is now enforced for the previously affected API endpoints by reviewing system logs or testing with controlled requests

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31990 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data