CVE-2025-2586: Ols: unauthenticated metrics flooding in openshift lightspeed service leading to resource exhaustion
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-2586 lets an unauthenticated party flood OpenShift Lightspeed Service with requests to invalid endpoints. The main impact is availability: metrics storage and processing can grow until CPU, memory, or disk pressure degrades monitoring or service stability.
Executive priority
Treat as a high-priority availability risk for OpenShift environments using Lightspeed. Focus first on externally reachable or shared clusters, because unauthenticated traffic can degrade monitoring and potentially affect cluster stability.
Technical view
The issue is CWE-400 resource consumption in OpenShift Lightspeed Service. Repeated unauthenticated API requests to non-existent endpoints inflate metrics workload and storage, causing excessive CPU, RAM, and disk usage. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, availability-only impact.
Likely exposure
Organizations using Red Hat OpenShift Lightspeed, specifically the lightspeed-service API package referenced by Red Hat, should assess exposure. The source bundle does not provide complete affected version ranges, and default status is listed as unaffected, so asset-level verification against Red Hat guidance is required.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not listed as KEV in the bundle. Exploitation would require network reachability to the vulnerable API surface, but not authentication, which increases concern for exposed or weakly restricted deployments.
Researcher notes
Evidence supports a resource-exhaustion flaw, but public details in the bundle do not define exact affected versions, fixed versions, or confirmed exploitation. Avoid assuming broader OpenShift impact beyond OpenShift Lightspeed Service unless Red Hat guidance confirms it.
Mitigation direction
Check Red Hat CVE guidance and the upstream pull request for applicable fixes.
Restrict OpenShift Lightspeed API exposure to trusted networks where operationally feasible.
Use ingress, route, or gateway controls to reduce unauthenticated request volume.
Monitor and alert on abnormal metrics storage growth and resource consumption.
Prioritize update or configuration changes once Red Hat confirms remediation details.
Validation and detection
Identify clusters running OpenShift Lightspeed or lightspeed-service API components.
Confirm whether the service is reachable without authentication from untrusted networks.
Review metrics storage growth, disk usage, CPU, and memory trends.
Look for high volumes of requests to non-existent endpoints.
Compare installed package state against Red Hat advisory and repository guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.