BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-54873High confidence

QUIC STREAM Fragment Metadata DoS

OpenSSL · OpenSSL

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.46% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs OpenSSL OpenSSL and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.3.5.7-1~deb13u3Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourceopensslNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourceopensslAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.3.6.5-1Debian Security Tracker ↗Source updated 7 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-54873 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: openssl: Denial of Service via excessive QUIC packet buffer retention
86 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
  • edk2-aarch64 as a component of Red Hat Enterprise Linux 10
  • edk2-ovmf as a component of Red Hat Enterprise Linux 10
  • edk2-tools as a component of Red Hat Enterprise Linux 10
  • edk2-tools-doc as a component of Red Hat Enterprise Linux 10
  • edk2.src as a component of Red Hat Enterprise Linux 10
  • mokutil as a component of Red Hat Enterprise Linux 10
  • openssl as a component of Red Hat Enterprise Linux 10
  • openssl-devel as a component of Red Hat Enterprise Linux 10
  • openssl-libs as a component of Red Hat Enterprise Linux 10
  • openssl-perl as a component of Red Hat Enterprise Linux 10
  • openssl.src as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in OpenSSL. A remote attacker can cause a Denial of Service (DoS) by sending specially crafted network packets to a QUIC protocol endpoint. Because the QUIC stack retains memory in packet buffers until the receiving application reads the stream data, an attacker can manipulate data transfers to keep these buffers allocated indefinitely. This behavior leads to excessive memory consumption and can exhaust available system resources.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-89005

No EUVD known-exploited evidence

Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

What

Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. 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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-770
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-89005Official EUVD mapping

Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3638OpenSSL: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in OpenSSL ausnutzen, um Sicherheitsvorkehrungen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren und einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1241Multiples vulnérabilités dans OpenSSL

De multiples vulnérabilités ont été découvertes dans OpenSSL. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 29 Sept 2026 · Last source change 30 Sept 2026, 20:11 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-30
European sourceENISA EUVD · EUVD-2026-89005
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    OpenSSL: 4.0.0 < 4.0.3, 3.6.0 < 3.6.5, 3.5.0 < 3.5.9, 3.4.0 < 3.4.8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    OpenSSL: 4.0.0 < 4.0.3, 3.6.0 < 3.6.5, 3.5.0 < 3.5.9, 3.4.0 < 3.4.8 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-54873 to remediation: access.redhat.com/CVE-2026-54873.
    Before
    remediation: access.redhat.com/CVE-2026-54873
    After
    remediation: access.redhat.com/CVE-2026-54873
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; edk2-aarch64 as a component of Red Hat Enterprise Linux 10; edk2-ovmf as a component of Red Hat Enterprise Linux 10; edk2-tools as a component of Red Hat Enterprise Linux 10; edk2-tools-doc as a component of Red Hat Enterprise Linux 10; edk2.src as a component of Red Hat Enterprise Linux 10; mokutil as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 10; openssl-devel as a component of Red Hat Enterprise Linux 10; openssl-libs as a component of Red Hat Enterprise Linux 10; openssl-perl as a component of Red Hat Enterprise Linux 10; openssl.src as a component of Red Hat Enterprise Linux 10; shim-aa64 as a component of Red Hat Enterprise Linux 10; shim-unsigned-aarch64.src as a component of Red Hat Enterprise Linux 10; shim-unsigned-x64.src as a component of Red Hat Enterprise Linux 10; shim-x64 as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 6; openssl-devel as a component of Red Hat Enterprise Linux 6; openssl-perl as a component of Red Hat Enterprise Linux 6; openssl-static as a component of Red Hat Enterprise Linux 6; openssl.src as a component of Red Hat Enterprise Linux 6; AAVMF as a component of Red Hat Enterprise Linux 7; OVMF as a component of Red Hat Enterprise Linux 7; mokutil as a component of Red Hat Enterprise Linux 7; openssl as a component of Red Hat Enterprise Linux 7; openssl-devel as a component of Red Hat Enterprise Linux 7; openssl-libs as a component of Red Hat Enterprise Linux 7; openssl-perl as a component of Red Hat Enterprise Linux 7; openssl-static as a component of Red Hat Enterprise Linux 7; openssl.src as a component of Red Hat Enterprise Linux 7; and 58 more
    After
    rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; edk2-aarch64 as a component of Red Hat Enterprise Linux 10; edk2-ovmf as a component of Red Hat Enterprise Linux 10; edk2-tools as a component of Red Hat Enterprise Linux 10; edk2-tools-doc as a component of Red Hat Enterprise Linux 10; edk2.src as a component of Red Hat Enterprise Linux 10; mokutil as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 10; openssl-devel as a component of Red Hat Enterprise Linux 10; openssl-libs as a component of Red Hat Enterprise Linux 10; openssl-perl as a component of Red Hat Enterprise Linux 10; openssl.src as a component of Red Hat Enterprise Linux 10; shim-aa64 as a component of Red Hat Enterprise Linux 10; shim-unsigned-aarch64.src as a component of Red Hat Enterprise Linux 10; shim-unsigned-x64.src as a component of Red Hat Enterprise Linux 10; shim-x64 as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 6; openssl-devel as a component of Red Hat Enterprise Linux 6; openssl-perl as a component of Red Hat Enterprise Linux 6; openssl-static as a component of Red Hat Enterprise Linux 6; openssl.src as a component of Red Hat Enterprise Linux 6; AAVMF as a component of Red Hat Enterprise Linux 7; OVMF as a component of Red Hat Enterprise Linux 7; mokutil as a component of Red Hat Enterprise Linux 7; openssl as a component of Red Hat Enterprise Linux 7; openssl-devel as a component of Red Hat Enterprise Linux 7; openssl-libs as a component of Red Hat Enterprise Linux 7; openssl-perl as a component of Red Hat Enterprise Linux 7; openssl-static as a component of Red Hat Enterprise Linux 7; openssl.src as a component of Red Hat Enterprise Linux 7; and 56 more · Fixed: openssl-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-0:3.5.9-0.1.hum1@src as a component of Red Hat Hardened Images; openssl-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl-config-fips-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-config-fips-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl-devel-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-devel-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl-devel-engine-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-devel-engine-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl-fips-provider-upstream-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-fips-provider-upstream-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl-libs-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-libs-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl-perl-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl-perl-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl3-0:3.5.9-0.1.hum1@src as a component of Red Hat Hardened Images; openssl3-devel-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl3-devel-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl3-devel-engine-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl3-devel-engine-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; openssl3-libs-0:3.5.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; openssl3-libs-0:3.5.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  5. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CISA ADP ↗
  6. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    7.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
    CISA ADP ↗
  7. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; edk2-aarch64 as a component of Red Hat Enterprise Linux 10; edk2-ovmf as a component of Red Hat Enterprise Linux 10; edk2-tools as a component of Red Hat Enterprise Linux 10; edk2-tools-doc as a component of Red Hat Enterprise Linux 10; edk2.src as a component of Red Hat Enterprise Linux 10; mokutil as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 10; openssl-devel as a component of Red Hat Enterprise Linux 10; openssl-libs as a component of Red Hat Enterprise Linux 10; openssl-perl as a component of Red Hat Enterprise Linux 10; openssl.src as a component of Red Hat Enterprise Linux 10; shim-aa64 as a component of Red Hat Enterprise Linux 10; shim-unsigned-aarch64.src as a component of Red Hat Enterprise Linux 10; shim-unsigned-x64.src as a component of Red Hat Enterprise Linux 10; shim-x64 as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 6; openssl-devel as a component of Red Hat Enterprise Linux 6; openssl-perl as a component of Red Hat Enterprise Linux 6; openssl-static as a component of Red Hat Enterprise Linux 6; openssl.src as a component of Red Hat Enterprise Linux 6; AAVMF as a component of Red Hat Enterprise Linux 7; OVMF as a component of Red Hat Enterprise Linux 7; mokutil as a component of Red Hat Enterprise Linux 7; openssl as a component of Red Hat Enterprise Linux 7; openssl-devel as a component of Red Hat Enterprise Linux 7; openssl-libs as a component of Red Hat Enterprise Linux 7; openssl-perl as a component of Red Hat Enterprise Linux 7; openssl-static as a component of Red Hat Enterprise Linux 7; openssl.src as a component of Red Hat Enterprise Linux 7; and 59 more
    After
    rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; edk2-aarch64 as a component of Red Hat Enterprise Linux 10; edk2-ovmf as a component of Red Hat Enterprise Linux 10; edk2-tools as a component of Red Hat Enterprise Linux 10; edk2-tools-doc as a component of Red Hat Enterprise Linux 10; edk2.src as a component of Red Hat Enterprise Linux 10; mokutil as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 10; openssl-devel as a component of Red Hat Enterprise Linux 10; openssl-libs as a component of Red Hat Enterprise Linux 10; openssl-perl as a component of Red Hat Enterprise Linux 10; openssl.src as a component of Red Hat Enterprise Linux 10; shim-aa64 as a component of Red Hat Enterprise Linux 10; shim-unsigned-aarch64.src as a component of Red Hat Enterprise Linux 10; shim-unsigned-x64.src as a component of Red Hat Enterprise Linux 10; shim-x64 as a component of Red Hat Enterprise Linux 10; openssl as a component of Red Hat Enterprise Linux 6; openssl-devel as a component of Red Hat Enterprise Linux 6; openssl-perl as a component of Red Hat Enterprise Linux 6; openssl-static as a component of Red Hat Enterprise Linux 6; openssl.src as a component of Red Hat Enterprise Linux 6; AAVMF as a component of Red Hat Enterprise Linux 7; OVMF as a component of Red Hat Enterprise Linux 7; mokutil as a component of Red Hat Enterprise Linux 7; openssl as a component of Red Hat Enterprise Linux 7; openssl-devel as a component of Red Hat Enterprise Linux 7; openssl-libs as a component of Red Hat Enterprise Linux 7; openssl-perl as a component of Red Hat Enterprise Linux 7; openssl-static as a component of Red Hat Enterprise Linux 7; openssl.src as a component of Red Hat Enterprise Linux 7; and 58 more
    Red Hat Product Security ↗
  9. ENISA EUVD mappingEUVD-2026-89005 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-89005"}
    ENISA EUVD ↗
  10. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-89005↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-54873 · cve.blacktree.nl