CVE-2025-14969 is a medium-severity (CVSS 4.3) CWE-772 vulnerability in org.hibernate.reactive:hibernate-reactive-core. A fix is available for org.hibernate.reactive:hibernate-reactive-core — see the affected versions and patch details below.
Hibernate Reactive Vulnerable to DoS via Connection Pool Exhaustion
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-2025-14969.
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.hibernate.reactive:hibernate-reactive-coreReal-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 flaw was found in Hibernate Reactive. When an HTTP endpoint is exposed to perform database operations, a remote client can prematurely close the HTTP connection. This action may lead to leaking connections from the database connection pool, potentially causing a Denial of Service (DoS) by exhausting available database connections.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.hibernate.reactive:hibernate-reactive-core | all versions | 4.2.1org.hibernate.reactive:hibernate-reactive-core:4.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hibernate.reactive:hibernate-reactive-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.hibernate.reactive:hibernate-reactive-core to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14969 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.
Frequently Asked Questions
Is CVE-2025-14969 in your dependencies?
Find it across Maven, including transitive dependencies.