CVE-2026-41007

Description

A flaw was found in Spring HATEOAS. An attacker can exploit this vulnerability by supplying specially crafted strings, which are then used as keys in an unbounded static cache. This can lead to resource exhaustion, causing a denial of service (DoS) for the application.

Statement

This is an Important denial of service flaw in Spring HATEOAS, affecting Red Hat JBoss Fuse. The vulnerability arises from an unbounded static cache that can be exhausted by attacker-supplied strings, leading to resource unavailability. This impact is considered Important due to the potential for remote, unauthenticated attackers to disrupt service.

Mitigation

To mitigate the risk of denial of service, restrict network access to applications that use Spring HATEOAS to trusted clients and networks. Implementing rate limiting on incoming requests can also help reduce the impact by limiting the volume of attacker-supplied strings that can trigger cache exhaustion. Ensure that any changes to network configurations are thoroughly tested to avoid disrupting legitimate service.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.