CVE-2025-14969VulnerabilityPublished 26 Jan 2026Updated 20 Oct 2026

CVE-2025-14969: Red Hat build of Quarkus 3.27.2.redhat · Missing Release of Resource after Effective Lifetime

Affects Red Hat build of Quarkus 3.27.2.redhatSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jan 2026
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-26.

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

Affected software

Product	Affected	Fixed in
Red HatRed Hat build of Quarkus 3.27.2.redhat	Affected–	Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform 8	Affected–	Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack	Affected–	Fixed in–
Red HatRed Hat OpenShift Dev Spaces	Affected–	Fixed in–

AI-suggested

1. Monitor database connection pool metrics closely to detect abnormal connection usage or leaks. 2. Implement connection timeout and maximum lifetime settings in the connection pool configuration to automatically reclaim leaked connections. 3. Restrict access to HTTP endpoints performing database operations to trusted clients or networks using network segmentation or firewall rules. 4. Employ rate limiting or throttling on HTTP endpoints to reduce the risk of connection exhaustion attacks. 5. Update to patched versions of Red Hat Quarkus build and Hibernate Reactive once available from Red Hat. 6. Conduct thorough testing of application behavior under premature connection closure scenarios to identify and address resource leaks. 7. Consider using circuit breakers or fallback mechanisms in the application to maintain availability during resource exhaustion. 8. Engage with Red Hat support for guidance and early access to fixes or workarounds.

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.

Impact

The primary impact of CVE-2025-14969 is a Denial of Service (DoS) condition caused by exhaustion of database connections in the connection pool. Organizations relying on Red Hat's Quarkus build with Hibernate Reactive may experience service disruptions or degraded performance when under attack or when clients inadvertently close connections prematurely. This can affect availability of critical applications, especially those with high traffic or those exposed to untrusted or public networks. While confidentiality and integrity are not directly impacted, the inability to process database requests can halt business operations, leading to potential financial losses, reputational damage, and operational downtime. The vulnerability could be exploited by remote attackers with minimal privileges, increasing the risk in multi-tenant or cloud environments. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as awareness grows.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 11:46 UTC

Technical details

References

Community reviews

Related threats