# Common Vulnerabilities and Exposures (CVE): Security vulnerabilities addressed in ElastiCache
Common Vulnerabilities and Exposures (CVE) is a list of entries for publicly known cybersecurity vulnerabilities. Each entry is a link that contains an identification number, a description, and at least one public reference. You can find on this page a list of security vulnerabilities that have been addressed in ElastiCache, as well as CVEs that do not affect ElastiCache.
We recommend that you always upgrade to the latest ElastiCache Valkey, Redis OSS or ElastiCache Memcached versions to be protected against known vulnerabilities. When operating an ElastiCache Serverless Cache, CVE fixes are automatically applied to your cache. When operating node-based clusters with Valkey or Redis OSS, ElastiCache exposes the PATCH component. For example, when using ElastiCache for Redis OSS version 6.2.6, the major version is 6, the minor version is 2, and the patch version is 6. PATCH versions are for backwards-compatible bug fixes, security fixes, and non-functional changes.
## CVEs addressed in Amazon ElastiCache
The following table lists CVEs and the ElastiCache engine versions in which they are addressed. A checkmark (✓) indicates the CVE is addressed in that version. N/A indicates the CVE does not affect that engine version. If your ElastiCache Valkey or Redis OSS cluster is running a version without the security fix, you can either upgrade to a more recent ElastiCache Valkey or Redis OSS version containing the fix, or if you are on a version containing the fix, ensure you have the latest service update applied by referring to [Managing service updates for node-based clusters](Self-Service-Updates.md#managing-updates). For more information about the supported ElastiCache engine versions and how to upgrade, see [Engine versions and upgrading in ElastiCache](engine-versions.md).
**Note**
An asterisk (\*) in the following table indicates you must have the latest service update applied for the cluster running the version specified in order to address the security vulnerability. For more information about how to verify you have the latest service update applied for the version your cluster is running on, see [Managing service updates for node-based clusters](Self-Service-Updates.md#managing-updates).
| CVE | Valkey 8.2 | Valkey 8.1 | Valkey 8.0 | Valkey 7.2 | Redis OSS 7.1 | Redis OSS 7.0 | Redis OSS 6.2 | Redis OSS 6.0 | Redis OSS 5.0 | Redis OSS 4.0 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [CVE-2026-25589](https://www.cve.org/CVERecord?id=CVE-2026-25589) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A |
| [CVE-2026-25588](https://www.cve.org/CVERecord?id=CVE-2026-25588) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A |
| [CVE-2026-25243](https://www.cve.org/CVERecord?id=CVE-2026-25243)\* | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A |
| [CVE-2026-23631](https://www.cve.org/CVERecord?id=CVE-2026-23631) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A |
| [CVE-2026-23479](https://www.cve.org/CVERecord?id=CVE-2026-23479)\* | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A |
| [CVE-2025-67733](https://www.cve.org/CVERecord?id=CVE-2025-67733)\* | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A | N/A |
| [CVE-2025-49844](https://www.cve.org/CVERecord?id=CVE-2025-49844)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-49819](https://www.cve.org/CVERecord?id=CVE-2025-49819)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-48367](https://www.cve.org/CVERecord?id=CVE-2025-48367)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-46844](https://www.cve.org/CVERecord?id=CVE-2025-46844)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-46818](https://www.cve.org/CVERecord?id=CVE-2025-46818)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-46817](https://www.cve.org/CVERecord?id=CVE-2025-46817)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-32023](https://www.cve.org/CVERecord?id=CVE-2025-32023)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2025-27151](https://www.cve.org/CVERecord?id=CVE-2025-27151)\* | N/A | ✓ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| [CVE-2025-21605](https://www.cve.org/CVERecord?id=CVE-2025-21605)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2024-46981](https://www.cve.org/CVERecord?id=CVE-2024-46981) | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2024-31449](https://www.cve.org/CVERecord?id=CVE-2024-31449)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2024-31228](https://www.cve.org/CVERecord?id=CVE-2024-31228)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2024-31227](https://www.cve.org/CVERecord?id=CVE-2024-31227)\* | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2023-41056](https://www.cve.org/CVERecord?id=CVE-2023-41056)\* | N/A | ✓ | ✓ | ✓ | ✓ | N/A | N/A | N/A | N/A | N/A |
| [CVE-2023-28425](https://www.cve.org/CVERecord?id=CVE-2023-28425)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | N/A | N/A | N/A | N/A |
| [CVE-2023-25155](https://www.cve.org/CVERecord?id=CVE-2023-25155) | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2023-22458](https://www.cve.org/CVERecord?id=CVE-2023-22458) | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2022-36021](https://www.cve.org/CVERecord?id=CVE-2022-36021)\* | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2022-35977](https://www.cve.org/CVERecord?id=CVE-2022-35977)\* | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2022-35951](https://www.cve.org/CVERecord?id=CVE-2022-35951)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | N/A | N/A | N/A | N/A |
| [CVE-2022-31144](https://www.cve.org/CVERecord?id=CVE-2022-31144)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | N/A | N/A | N/A | N/A |
| [CVE-2022-24834](https://www.cve.org/CVERecord?id=CVE-2022-24834)\* | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| [CVE-2021-41099](https://www.cve.org/CVERecord?id=CVE-2021-41099)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32762](https://www.cve.org/CVERecord?id=CVE-2021-32762)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32761](https://www.cve.org/CVERecord?id=CVE-2021-32761)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32687](https://www.cve.org/CVERecord?id=CVE-2021-32687)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32675](https://www.cve.org/CVERecord?id=CVE-2021-32675)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32672](https://www.cve.org/CVERecord?id=CVE-2021-32672)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32628](https://www.cve.org/CVERecord?id=CVE-2021-32628)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32627](https://www.cve.org/CVERecord?id=CVE-2021-32627)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32626](https://www.cve.org/CVERecord?id=CVE-2021-32626)\* | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-32625](https://www.cve.org/CVERecord?id=CVE-2021-32625)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-29478](https://www.cve.org/CVERecord?id=CVE-2021-29478)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-29477](https://www.cve.org/CVERecord?id=CVE-2021-29477)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
| [CVE-2021-21309](https://www.cve.org/CVERecord?id=CVE-2021-21309)\* | N/A | N/A | N/A | N/A | ✓ | ✓ | ✓ | ✓ | N/A | N/A |
## CVEs that do not affect Amazon ElastiCache
The following CVEs do not affect Amazon ElastiCache for Valkey or Redis OSS.
+ [CVE-2026-21864](https://www.cve.org/CVERecord?id=CVE-2026-21864)
+ [CVE-2026-21863](https://www.cve.org/CVERecord?id=CVE-2026-21863)
+ [CVE-2024-51741](https://www.cve.org/CVERecord?id=CVE-2024-51741)
+ [CVE-2023-45145](https://www.cve.org/CVERecord?id=CVE-2023-45145)
+ [CVE-2023-28856](https://www.cve.org/CVERecord?id=CVE-2023-28856)
+ [CVE-2022-24736](https://www.cve.org/CVERecord?id=CVE-2022-24736)
+ [CVE-2022-24735](https://www.cve.org/CVERecord?id=CVE-2022-24735)