Skip to content
Fencer Intel
high 7.5

CVE-2025-2240 json

Smallrye-fault-tolerance: smallrye fault tolerance

published last yr. modified 5d ago also EUVD-2025-6307 , GHSA-gfh6-3pqw-x2j4

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.smallrye:smallrye-fault-tolerance-core 6.4.2, 6.9.0
  • smallrye smallrye-fault-tolerance-core 6.4.2, 6.9.0

Is CVE-2025-2240 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-2240 updated cvss 7.5

smallrye-fault-tolerance: SmallRye Fault Tolerance

  • Red Hat build of Apicurio Registry 2 smallrye-fault-tolerance-core
    affected: workaround, no fix available “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.”
  • Red Hat Fuse 7 smallrye-fault-tolerance-core Red Hat Integration Camel K 1 smallrye-fault-tolerance-core Red Hat JBoss Enterprise Application Platform 7 smallrye-fault-tolerance-core
    affected: workaround, no fix planned “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.”
  • Red Hat Build of Apache Camel 4.8 for Quarkus 3.15
    fixed: vendor fix “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.” RHSA-2025:3541
  • Red Hat build of Apache Camel 4.8.5 for Spring Boot
    fixed: vendor fix “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.” RHSA-2025:3543
  • Red Hat build of Quarkus 3.15.4
    fixed: vendor fix “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.” RHSA-2025:3376
  • Red Hat build of Apicurio Registry 3 smallrye-fault-tolerance-core Red Hat build of Quarkus smallrye-fault-tolerance-apiimpl Red Hat JBoss Enterprise Application Platform 8 smallrye-fault-tolerance-core Red Hat JBoss Enterprise Application Platform Expansion Pack smallrye-fault-tolerance-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven io.smallrye:smallrye-fault-tolerance-core
>=6.3.0, <6.4.2
>=6.5.0, <6.9.0
6.4.2
6.9.0

Affected products

  • smallrye smallrye-fault-tolerance-core
  • Red Hat Red Hat build of Apache Camel 4.8.5 for Spring Boot
  • Red Hat Red Hat Build of Apache Camel 4.8 for Quarkus 3.15
  • Red Hat Red Hat build of Quarkus 3.15.4
  • Red Hat Red Hat build of Apicurio Registry 2
  • Red Hat Red Hat build of Apicurio Registry 3
  • Red Hat Red Hat build of Quarkus
  • Red Hat Red Hat Fuse 7
  • Red Hat Red Hat Integration Camel K 1
  • Red Hat Red Hat JBoss Enterprise Application Platform 7
  • Red Hat Red Hat JBoss Enterprise Application Platform 8
  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack

Classification

Weakness
  • CWE-1325 Improperly Controlled Sequential Memory Allocation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.