Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

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

HIGH

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
Aug 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 18, 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.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2025-2240 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
io.smallrye:smallrye-fault-tolerance-coreio.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
EcosystemPackageVulnerable rangeFix
Mavenio.smallrye:smallrye-fault-tolerance-core6.3.0&&< 6.4.26.4.2io.smallrye:smallrye-fault-tolerance-core:6.4.2
Mavenio.smallrye:smallrye-fault-tolerance-core6.5.0&&< 6.9.06.9.0io.smallrye:smallrye-fault-tolerance-core:6.9.0

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-2240 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-2240. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

ProductFixed inAdvisory
Red Hat build of Apache Camel 4.8.5 for Spring Bootsmallrye-fault-tolerance-coreRHSA-2025:3543
Red Hat Build of Apache Camel 4.8 for Quarkus 3.15quarkus-camel-bomRHSA-2025:3541
Red Hat build of Quarkus 3.15.4smallrye-fault-tolerance-coreRHSA-2025:3376

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-2240 in your dependencies?

O3 Security finds CVE-2025-2240 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2025-2240: DoS (High 7.5) | O3 Security