LiveActive security incident?Get immediate response
CVE Record

CVE-2025-2240: 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.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
high
Sources
8

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-2240 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
5Timeline events
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-2240Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Made public.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorsmallrye-fault-tolerance-coresmallrye-fault-tolerance-core, 6.3.0, 6.5.0unaffected
Red HatRed Hat build of Apache Camel 4.8.5 for Spring Bootio.smallrye/smallrye-fault-tolerance-coreunaffected
Red HatRed Hat Build of Apache Camel 4.8 for Quarkus 3.15com.redhat.quarkus.platform/quarkus-camel-bomunaffected
Red HatRed Hat Build of Apache Camel 4.8 for Quarkus 3.15com.redhat.quarkus.platform/quarkus-cxf-bomunaffected
Red HatRed Hat build of Quarkus 3.15.4See advisoryunaffected
Red HatRed Hat build of Apicurio Registry 2io.smallrye/smallrye-fault-tolerance-coreaffected
Red HatRed Hat build of Apicurio Registry 3io.smallrye/smallrye-fault-tolerance-coreaffected
Red HatRed Hat build of Quarkusio.smallrye/smallrye-fault-tolerance-apiimplunaffected
Red HatRed Hat build of Quarkusio.smallrye/smallrye-fault-tolerance-coreunaffected
Red HatRed Hat Fuse 7io.smallrye/smallrye-fault-tolerance-coreunknown
Red HatRed Hat Integration Camel K 1io.smallrye/smallrye-fault-tolerance-coreaffected
Red HatRed Hat JBoss Enterprise Application Platform 7smallrye-fault-tolerance-coreaffected
Red HatRed Hat JBoss Enterprise Application Platform 8smallrye-fault-tolerance-coreunaffected
Red HatRed Hat JBoss Enterprise Application Platform Expansion Packsmallrye-fault-tolerance-coreunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1325 · source CWE mapping

Improperly Controlled Sequential Memory Allocation

Improperly Controlled Sequential Memory Allocation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.