CVE-2024-8391VulnerabilityPublished 21 Jan 2025Updated 7 Sep 2026

Red Hat Security Advisory: JBoss EAP XP 5.0 Update 1.0 release. See references for release notes

Affects Red HatSource GCVE Database

Not known to be exploited : upgrade to 5.0.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.1

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Red Hat to 5.0.1.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=5.0.0 <5.0.1	Fixed in 5.0.1

AI-suggested

Red Hat has released JBoss EAP XP 5.0 Update 1.0 which includes a fix for CVE-2024-8391. Users of affected versions (>=5.0.0 <5.0.1) should apply this update following the official Red Hat documentation. No additional mitigation steps are indicated by the vendor advisory.

Description

A security vulnerability identified as CVE-2024-8391 affects the Vertx gRPC server component in Red Hat JBoss Enterprise Application Platform (EAP) XP 5.0. The issue is that the Vertx gRPC server does not limit the maximum message size, which could lead to resource exhaustion or denial of service conditions. Red Hat has released JBoss EAP XP 5.0 Update 1.0 to address this vulnerability. The advisory rates the severity as moderate and no CVSS score is provided.

Impact

The vulnerability could allow an attacker to cause resource exhaustion on the affected system by sending gRPC messages that exceed expected size limits. This may result in denial of service or degraded performance of the JBoss EAP XP 5.0 server. No known exploits in the wild have been reported at this time.

Summary

CVE-2024-8391 is a vulnerability in the io.vertx/vertx-grpc server used by Red Hat JBoss EAP XP 5.0 where the server does not enforce a maximum message size limit. This could allow an attacker to send excessively large messages, potentially leading to resource exhaustion or denial of service. Red Hat has issued JBoss EAP XP 5.0 Update 1.0 as a security fix to address this issue. The vulnerability is categorized under CWE-770 (Allocation of Resources Without Limits or Throttling).

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Sep 2026, 17:04 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats