Skip to content
Noroxi
CVE-2025-2240· NVD / CVE Program· CNA redhat

Smallrye-fault-tolerance: smallrye fault tolerance

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Mar 12, 2025
Updated
Aug 13, 2026
EPSS
1.0% · 62th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • github.com/smallrye/smallrye-fault-tolerance smallrye-fault-tolerance-core

    • 6.3.0 and later · before 6.4.2affected · semver
    • 6.5.0 and later · before 6.9.0affected · semver

  • Red Hat Red Hat Build of Apache Camel 4.8 for Quarkus 3.15

    • all versionsunknown
    • all versionsunknown

  • Red Hat Red Hat build of Apache Camel 4.8.5 for Spring Boot

    • all versionsunknown

  • Red Hat Red Hat build of Apicurio Registry 2

    • all versionsaffected

  • Red Hat Red Hat build of Apicurio Registry 3

    • all versionsunknown

  • Red Hat Red Hat build of Quarkus

    • all versionsunknown

  • Red Hat Red Hat build of Quarkus 3.15.4

    • all versionsunknown

  • Red Hat Red Hat Fuse 7

    • all versionsunknown

  • Red Hat Red Hat Integration Camel K 1

    • all versionsaffected

  • Red Hat Red Hat JBoss Enterprise Application Platform 7

    • all versionsaffected

  • Red Hat Red Hat JBoss Enterprise Application Platform 8

    • all versionsunknown

  • Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack

    • all versionsunknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenio.smallrye:smallrye-fault-tolerance-corefrom 6.3.0 · before 6.4.26.4.2
Mavenio.smallrye:smallrye-fault-tolerance-corefrom 6.5.0 · before 6.9.06.9.0

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
github.com/smallrye/smallrye-fault-tolerance smallrye-fault-tolerance-core6.4.2Vendor (CNA)
github.com/smallrye/smallrye-fault-tolerance smallrye-fault-tolerance-core6.9.0Vendor (CNA)
Maven:io.smallrye:smallrye-fault-tolerance-core6.4.2Package registry (OSV)
Maven:io.smallrye:smallrye-fault-tolerance-core6.9.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-1325 · Improperly Controlled Sequential Memory Allocation

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records