{"id":310283,"date":"2025-11-22T04:08:13","date_gmt":"2025-11-22T04:08:13","guid":{"rendered":"https:\/\/peraltafinancing.com\/business\/internet-business\/redis-security-advisory\/"},"modified":"2025-11-22T04:08:13","modified_gmt":"2025-11-22T04:08:13","slug":"redis-security-advisory","status":"publish","type":"post","link":"https:\/\/fivemor.com\/?p=310283","title":{"rendered":"Redis Security Advisory."},"content":{"rendered":"


\n<\/p>\n

\n
\n<\/header>\n
\n
\"Websites<\/figure>\n

The following advisory has been put out for any customer servers using Redis within their setup.<\/p>\n

What happened?<\/strong><\/p>\n

As part of an ongoing effort by Redis and the Redis community to maintain Redis\u2019 safety, security, and compliance posture, a security vulnerability in Redis has been identified and remediated in the versions indicated below.<\/p>\n

What is the vulnerability?<\/strong><\/p>\n

[<\/strong>CVE-2025-49844<\/strong><\/a>]<\/strong>\u00a0Lua use-after-free may lead to remote code execution.\u00a0CVSS Score: 10.0 (Critical)<\/strong><\/p>\n

An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution.<\/p>\n

How can you protect your Redis instance?<\/strong><\/p>\n

Exploitation of this vulnerability requires an attacker to first gain authenticated access to your Redis instance.<\/p>\n

There are several steps you can take to protect your Redis from being accessed by a malicious actor. To minimize the risk of exploitation, it\u2019s important to follow these best practices:<\/p>\n