alsa-2025:11401
Vulnerability from osv_almalinux
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 Stack Buffer Overflow (CVE-2025-27151)
- redis: Redis Unauthenticated Denial of Service (CVE-2025-48367)
- redis: Redis Hyperloglog Out-of-Bounds Write Vulnerability (CVE-2025-32023)
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.
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "valkey"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.0.4-1.el10_0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "valkey-devel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.0.4-1.el10_0"
}
],
"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 Stack Buffer Overflow (CVE-2025-27151)\n * redis: Redis Unauthenticated Denial of Service (CVE-2025-48367)\n * redis: Redis Hyperloglog Out-of-Bounds Write Vulnerability (CVE-2025-32023)\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-2025:11401",
"modified": "2025-07-28T15:46:39Z",
"published": "2025-07-21T00:00:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2025:11401"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2025-27151"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2025-32023"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2025-48367"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2369153"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/10/ALSA-2025-11401.html"
}
],
"related": [
"CVE-2025-27151",
"CVE-2025-48367",
"CVE-2025-32023"
],
"summary": "Important: valkey security update"
}
Sightings
| Author | Source | Type | Date |
|---|
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.