CVE-2026-14456VulnerabilityPublished 18 Aug 2026Updated 30 Oct 2026

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Affects Red HatSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 11:52 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

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

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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 Hat Product Security Red Hat	Affected Red Hat Red Hat Hardened Images aarch64 openssl-1:3.5.6-0.5.hum1@aarch64	Fixed in–

AI-suggested

Red Hat recommends first confirming if a QUIC server listener is active on UDP port 443. If so, immediate mitigation includes blocking or rate-limiting UDP 443 traffic at the firewall or network edge to slow or block malicious QUIC Initial packets. If QUIC/HTTP3 is not required, disabling the QUIC server listener entirely is advised. Application owners can also adjust the SSL_VALUE_QUIC_MAX_PENDING_CONNS parameter if the default limit is too high. Finally, upgrading OpenSSL to the fixed version 3.5.6-0.5.hum1 when available will resolve the vulnerability.

Description

A vulnerability in OpenSSL 3.5.x affects the QUIC server implementation used in Red Hat Hardened Images and certain Red Hat Enterprise Linux versions. A remote attacker can send many QUIC Initial packets to cause unbounded memory growth on the server, leading to denial of service by exhausting memory resources. The flaw requires the QUIC server listener to be explicitly enabled; systems not running a QUIC listener on UDP port 443 are not affected. Mitigations include firewall rules to rate-limit or block UDP 443 traffic and disabling the QUIC server if not needed. A fixed OpenSSL update is available in version 3.5.6-0.5.hum1.

Impact

The vulnerability can cause unbounded memory growth on an OpenSSL QUIC server, leading to denial of service by exhausting system memory and making the QUIC listener unavailable. This impacts availability but does not affect confidentiality or integrity. Only systems running OpenSSL 3.5.x with an enabled QUIC server listener on UDP port 443 are affected. Systems not listening on UDP 443 or running earlier OpenSSL versions without QUIC support are not impacted.

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).
CWE-772Missing Release of Resource after Effective Lifetime (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including…
Operation · Architecture and Design · Resource Limitation
Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available.
Attack patterns
HTTP DoS (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 30 Oct 2026, 09:59 UTC

WeaknessesCWE-770, CWE-772

Technical details

References

Community reviews

Related threats