How severe is CVE-2025-2240?

CVE-2025-2240 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-2240?

CVE-2025-2240 affects the following packages: io.smallrye:smallrye-fault-tolerance-core (Maven), io.smallrye:smallrye-fault-tolerance-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-2240?

Update io.smallrye:smallrye-fault-tolerance-core to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2240 is resolved across your whole dependency graph.

How do I detect CVE-2025-2240 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.smallrye:smallrye-fault-tolerance-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-2240 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-2240 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-2240 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-2240?

CVE-2025-2240 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-2240?

CVE-2025-2240 is classified as CWE-1325 (CWE-1325). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-2240 published, and has it been updated?

CVE-2025-2240 was published on March 12, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2025-2240 — smallrye-fault-tolerance-…

HIGHFix: smallrye/smallrye-fault-tolerance#985

CVE-2025-2240 is a high-severity (CVSS 7.5) CWE-1325 vulnerability in io.smallrye:smallrye-fault-tolerance-core. A fix is available for io.smallrye:smallrye-fault-tolerance-core — see the affected versions and patch details below.

Smallrye-fault-tolerance: smallrye fault tolerance

Also known asGHSA-gfh6-3pqw-x2j4

Published

Mar 12, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-2240.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕io.smallrye:smallrye-fault-tolerance-core☕io.smallrye:smallrye-fault-tolerance-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.smallrye:smallrye-fault-tolerance-core`	≥ 6.3.0&&< 6.4.2	6.4.2`io.smallrye:smallrye-fault-tolerance-core:6.4.2`
☕Maven	`io.smallrye:smallrye-fault-tolerance-core`	≥ 6.5.0&&< 6.9.0	6.9.0`io.smallrye:smallrye-fault-tolerance-core:6.9.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.smallrye:smallrye-fault-tolerance-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.smallrye:smallrye-fault-tolerance-core to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2240 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability allows a remote attacker to cause an out-of-memory issue when calling the metrics URI, resulting in a denial of service. As this flaw can be triggered via the network, it has been rated with an important severity.

Workaround published by Red Hat

Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

Source: Red Hat security advisory for CVE-2025-2240 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Apache Camel 4.8.5 for Spring Boot	`smallrye-fault-tolerance-core`	RHSA-2025:3543
Red Hat Build of Apache Camel 4.8 for Quarkus 3.15	`quarkus-camel-bom`	RHSA-2025:3541
Red Hat build of Quarkus 3.15.4	`smallrye-fault-tolerance-core`	RHSA-2025:3376

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-2240 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works