A flaw was found in Smallrye, where smallrye-fault-tolerance is vulnerable to an out-of-memory (OOM) issue. This vulnerability is externally triggered when calling the metrics URI. Every call creates a new object within meterMap and may lead to a denial of service (DoS) issue.
Security readout for executives and security teams
Plain-English summary
CVE-2025-2240 is a denial-of-service flaw in SmallRye Fault Tolerance. Calls to the metrics URI can create new objects without proper control, consuming memory until the service may fail. The business risk is service outage, especially where metrics endpoints are reachable without strong access controls.
Executive priority
Prioritize remediation for internet-facing or partner-facing services where metrics endpoints are exposed. This is not described as data theft or code execution, but it can cause outage. Internal-only deployments still need review because monitoring endpoints are often broadly reachable inside networks.
Technical view
SmallRye Fault Tolerance can allocate a new object in meterMap on each metrics URI call, leading to out-of-memory conditions. The CVSS 3.1 score is 7.5 with network attack vector, low complexity, no privileges, no user interaction, and high availability impact.
Likely exposure
Most likely exposed in Java services using affected smallrye-fault-tolerance-core versions 6.3.0 or 6.5.0, or affected Red Hat products such as Apicurio Registry 2/3, Camel K 1, and JBoss EAP 7. Actual exposure depends on whether the metrics URI is reachable.
Exploitation context
The source bundle states the issue is externally triggered through metrics URI calls. CISA KEV is false, and the provided sources do not show active exploitation. The CVSS vector indicates unauthenticated network reachability, but no exploit details are needed to assess outage risk.
Researcher notes
Evidence is strongest for availability impact through uncontrolled allocation during metrics access. The bundle names affected upstream versions and several Red Hat product statuses, but it does not provide detailed fixed version mapping for every product. Avoid assuming all SmallRye consumers are affected without dependency and endpoint validation.
Mitigation direction
Apply relevant vendor updates from Red Hat advisories RHSA-2025:3376, RHSA-2025:3541, and RHSA-2025:3543.
Update affected SmallRye Fault Tolerance components when fixed versions are available from your vendor.
Restrict metrics URI access to trusted networks, authenticated monitoring systems, or internal service paths.
Review Red Hat’s CVE page for product-specific status before changing unaffected components.
For Red Hat Fuse 7, treat status as unknown and confirm with vendor guidance.
Validation and detection
Inventory services using smallrye-fault-tolerance-core or related Red Hat packaged components.
Compare deployed product status against the affected and unaffected entries in the source bundle.
Confirm whether the metrics URI is reachable from untrusted networks or unauthenticated clients.
Check service memory trends and request logs for abnormal metrics endpoint activity.
After updating, verify installed component versions against the applicable Red Hat advisory.
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-1325: 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.
Improperly Controlled Sequential Memory Allocation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.