CVE-2024-8447 is a medium-severity (CVSS 5.9) CWE-833 vulnerability in org.jboss.narayana.rts:lra-coordinator-jar. A fix is available for org.jboss.narayana.rts:lra-coordinator-jar — see the affected versions and patch details below.
Narayana: deadlock via multiple join requests sent to lra coordinator
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-2024-8447.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jboss.narayana.rts:lra-coordinator-jarReal-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 security issue was discovered in the LRA Coordinator component of Narayana. When Cancel is called in LRA, an execution time of approximately 2 seconds occurs. If Join is called with the same LRA ID within that timeframe, the application may crash or hang indefinitely, leading to a denial of service.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jboss.narayana.rts:lra-coordinator-jar | all versions | 7.1.0.Finalorg.jboss.narayana.rts:lra-coordinator-jar:7.1.0.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.narayana.rts:lra-coordinator-jar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.narayana.rts:lra-coordinator-jar to 7.1.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-8447 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss EAP XP 5.0 Update 2.0 | org.jboss.narayana-narayana-all | RHSA-2025:7620 |
| Red Hat JBoss Enterprise Application Platform 8 | org.jboss.narayana-narayana-all | RHSA-2025:3358 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8 | eap8-eap-product-conf-parent-0:800.6.1-1.GA_redhat_00001.1.el8eap | RHSA-2025:3357 |
Frequently Asked Questions
Is CVE-2024-8447 in your dependencies?
Find it across Maven, including transitive dependencies.