Vulnerability from bitnami_vulndb
Published
2026-08-24 05:53
Modified
2026-08-24 06:09
Summary
Valkey: TLS pending-data processing use-after-free may allow remote code execution
Details

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.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "valkey",
        "purl": "pkg:bitnami/valkey"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.14"
            },
            {
              "introduced": "8.0.0"
            },
            {
              "fixed": "8.0.10"
            },
            {
              "introduced": "8.1.0"
            },
            {
              "fixed": "8.1.9"
            },
            {
              "introduced": "9.0.0"
            },
            {
              "fixed": "9.0.5"
            },
            {
              "introduced": "9.1.0"
            },
            {
              "fixed": "9.1.1"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-56684"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:valkey-io:valkey:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "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\u0027s tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator\u0027s 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.",
  "id": "BIT-valkey-2026-56684",
  "modified": "2026-08-24T06:09:24.796Z",
  "published": "2026-08-24T05:53:58.352Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/commit/7cd5bcb7575d750ec2de618db80da58680a10fe3"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/pull/4234"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/releases/tag/7.2.14"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/releases/tag/8.0.10"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/releases/tag/8.1.9"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/releases/tag/9.0.5"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/releases/tag/9.1.1"
    },
    {
      "type": "WEB",
      "url": "https://github.com/valkey-io/valkey/security/advisories/GHSA-53mc-f3m3-99vh"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56684"
    }
  ],
  "schema_version": "1.6.2",
  "summary": "Valkey: TLS pending-data processing use-after-free may allow remote code execution"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.