GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration
alsa-2026:64807
Vulnerability from osv_almalinux
Published
2026-09-08 00:00
Modified
2026-09-09 07:46
Summary
Important: valkey security, bug fix, and enhancement update
Details

Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.

Security Fix(es):

  • redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)
  • valkey: Valkey: Remote code execution via use-after-free in stream deserialization (CVE-2026-63639)
  • valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free (CVE-2026-56684)

Bug Fix(es) and Enhancement(s):

  • [Tracker] Rebase valkey to 8.0.10 (JIRA:AlmaLinux-216778)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

References
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "AlmaLinux:9",
        "name": "valkey"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "8.0.10-1.el9_8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "AlmaLinux:9",
        "name": "valkey-devel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "8.0.10-1.el9_8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "Valkey is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Valkey works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Valkey also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Valkey behave like a cache. You can use Valkey from most programming languages also.  \n\nSecurity Fix(es):  \n\n  * redis: Redis: Remote Code Execution via specially crafted RESTORE payload (CVE-2026-66373)\n  * valkey: Valkey: Remote code execution via use-after-free in stream deserialization (CVE-2026-63639)\n  * valkey: Valkey: Remote code execution via TLS pending-data processing use-after-free (CVE-2026-56684)\n\n\nBug Fix(es) and Enhancement(s):  \n\n  * [Tracker] Rebase valkey to 8.0.10 (JIRA:AlmaLinux-216778)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n",
  "id": "ALSA-2026:64807",
  "modified": "2026-09-09T07:46:29Z",
  "published": "2026-09-08T00:00:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://access.redhat.com/errata/RHSA-2026:64807"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-56684"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-63639"
    },
    {
      "type": "REPORT",
      "url": "https://access.redhat.com/security/cve/CVE-2026-66373"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2506985"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2517906"
    },
    {
      "type": "REPORT",
      "url": "https://bugzilla.redhat.com/2517907"
    },
    {
      "type": "ADVISORY",
      "url": "https://errata.almalinux.org/9/ALSA-2026-64807.html"
    }
  ],
  "related": [
    "CVE-2026-66373",
    "CVE-2026-63639",
    "CVE-2026-56684"
  ],
  "summary": "Important: valkey security, bug fix, and enhancement update"
}



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.