Red Hat OpenShift Lightspeed Service API resource consumption

Summaryinfo

A vulnerability identified as critical has been detected in Red Hat OpenShift Lightspeed Service. This affects an unknown function of the component API. This manipulation causes resource consumption. This vulnerability is handled as CVE-2025-2586. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Red Hat OpenShift Lightspeed Service (affected version not known). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component API. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

A flaw was found in the OpenShift Lightspeed Service, which is vulnerable to unauthenticated API request flooding. Repeated queries to non-existent endpoints inflate metrics storage and processing, consuming excessive resources. This issue can lead to monitoring system degradation, increased disk usage, and potential service unavailability. Since the issue does not require authentication, an external attacker can exhaust CPU, RAM, and disk space, impacting both application and cluster stability.

The advisory is shared at access.redhat.com. This vulnerability is known as CVE-2025-2586 since 03/21/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/08/2025). MITRE ATT&CK project uses the attack technique T1499 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-8735). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Virtualization Software

Vendor

• Red Hat

Name

• OpenShift Lightspeed Service

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion