Skip to main content
VulnerabilityPublished Updated

CVE-2025-46817: valkey security update

Affects valkeySource GCVE Database

0
Compare

Not known to be exploited · public detection template (Nuclei) : upgrade to 8.0.6-1.el10_0 soon.

Data as of 4 Nov 2026, 18:42 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Patch
Available – fixed in 8.0.6-1.el10_0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2025

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade the AlmaLinux to 8.0.6-1.el10_0.

Affected software

ProductAffectedFixed in
AlmaLinux 10valkeyAffected
  • <8.0.6-1.el10_0
Fixed in
  • 8.0.6-1.el10_0
AlmaLinux 10valkey-develAffected
  • <8.0.6-1.el10_0
Fixed in
  • 8.0.6-1.el10_0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update is available and should be applied to upgrade Valkey to version 8.0.6-1.el10_0 or later. This update addresses CVE-2025-46817 and related Lua scripting vulnerabilities. Users should follow Red Hat's official guidance for applying the update as detailed in their advisory. No additional mitigation steps are indicated beyond applying the patch.

Description

Valkey, an advanced key-value store, has a security vulnerability (CVE-2025-46817) involving Lua library commands that may cause integer overflow and potentially lead to remote code execution. This issue affects versions prior to 8.0.6-1.el10_0. The vulnerability is part of a set of Lua-related security flaws addressed in the update. A patch is available to fix this issue.

References

Community reviews

Loading reviews…