CVE-2025-46817 is an integer-overflow vulnerability in the Lua scripting functionality of Redis. An authenticated user can submit a specially crafted Lua script that triggers the overflow and may achieve remote code execution. The issue affects Redis versions 8.2.1 and earlier that include Lua scripting support.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical vulnerability tracked as CVE-2025-46817, covered by an Alma Linux 9.2 TuxCare local security-check advisory. The provided content does not identify the affected software component or vulnerability mechanism.
A high-severity integer overflow vulnerability in Valkey's Lua scripting functionality that allows local code execution by a low-privileged adversary.
A high-severity integer overflow vulnerability in Redis Lua scripting that allows local, low-privileged adversaries to achieve remote code execution via a crafted Lua script.
An authenticated remote code execution vulnerability in Redis Lua script handling caused by integer overflow during Lua script execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.