Skip to content
VulniPulse
Sign in
Highest advisory severityHigh 1 vendor · 1 advisory

CVE-2026-56684

CVE-2026-56684: 1 tracked advisory record across Red Hat. Compare vendor sources and published fix guidance.

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

NVD detail CVE.org

Vendor advisory comparison

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-56684] Remote code execution via TLS pending-data processing use-after-free

    CVE-2026-56684Source published Source updated

    Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1. A flaw was found in Valkey. This flaw, when Transport Layer Security (TLS) is enabled, may result in a server crash or potentially allow a remote attacker to achieve arbitrary code execution. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-825. Affected Red Hat products: Red…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10.0 Extended Update Support
    • Red Hat Enterprise Linux 9
    • Red Hat Hardened Images
    • Red Hat package: valkey
    Source-reported affected versions
    • < 7.2.14
    • < 8.0.10
    • < 8.1.9
    • < 9.0.5

    1 more entries in the full advisory.

    Source-reported fixed versions
    • 7.2.14
    • 8.0.10
    • 8.1.9
    • 9.0.5

    9 more entries in the full advisory.

    Mitigation guidance
    • Restrict network access to the Valkey instance to trusted clients and networks by configuring firewall rules to limit inbound connections to the Valkey service port. Ensure only authorized and authenticated clients can connect. If TLS is not strictly required, consider disabling it. These network restrictions will persist if the Valkey service is reloaded or restarted.
    Full advisory and evidenceOpen source bulletin

Android app · Google Play

Monitor future Red Hat CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features