Loading vulnerability…
CVE-2025-46818 is a code-injection vulnerability in Redis Lua scripting. Redis versions 8.2.1 and earlier permit an authenticated user to submit a specially crafted Lua script that manipulates Lua objects and may execute attacker-controlled code in the context of another user. The issue affects Redis versions with Lua scripting and is fixed in Redis 8.2.2.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An important-severity vulnerability addressed by the referenced Alma Linux 9.2 TuxCare security advisory. The supplied content does not identify the affected component or technical flaw type.
A vulnerability identified as CVE-2025-46818, for which impact and remediation information has been added to a Nuclei template. The specific technical details are not provided in the content, but the existence of a template and remediation guidance suggests it is a notable security issue.
A medium-severity vulnerability in Valkey's Lua scripting that allows local code execution in the context of another user.
A medium-severity vulnerability in Redis Lua scripting allowing local, low-privileged adversaries to execute arbitrary code in the context of another user via crafted Lua scripts.
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.