Bug 2401322 (CVE-2025-46819) - CVE-2025-46819 Redis: Redis is vulnerable to DoS via specially crafted LUA scripts
Summary: CVE-2025-46819 Redis: Redis is vulnerable to DoS via specially crafted LUA sc...
Keywords:
Status: NEW
Alias: CVE-2025-46819
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-03 20:01 UTC by OSIDB Bzimport
Modified: 2025-11-28 08:35 UTC (History)
83 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:19237 0 None None None 2025-10-29 09:34:12 UTC
Red Hat Product Errata RHSA-2025:19238 0 None None None 2025-10-29 09:28:34 UTC
Red Hat Product Errata RHSA-2025:19345 0 None None None 2025-10-30 14:07:04 UTC
Red Hat Product Errata RHSA-2025:19675 0 None None None 2025-11-04 14:38:32 UTC
Red Hat Product Errata RHSA-2025:20926 0 None None None 2025-11-11 13:50:55 UTC
Red Hat Product Errata RHSA-2025:20955 0 None None None 2025-11-11 14:59:55 UTC
Red Hat Product Errata RHSA-2025:21916 0 None None None 2025-11-24 01:59:11 UTC
Red Hat Product Errata RHSA-2025:21936 0 None None None 2025-11-24 09:41:40 UTC

Description OSIDB Bzimport 2025-10-03 20:01:19 UTC 
Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted LUA script to read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to block a script by restricting both the EVAL and FUNCTION command families.
Comment 5 errata-xmlrpc 2025-10-29 09:28:27 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:19238 https://access.redhat.com/errata/RHSA-2025:19238
Comment 6 errata-xmlrpc 2025-10-29 09:34:06 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:19237 https://access.redhat.com/errata/RHSA-2025:19237
Comment 7 errata-xmlrpc 2025-10-30 14:06:59 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:19345 https://access.redhat.com/errata/RHSA-2025:19345
Comment 8 errata-xmlrpc 2025-11-04 14:38:26 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:19675 https://access.redhat.com/errata/RHSA-2025:19675
Comment 9 errata-xmlrpc 2025-11-11 13:50:50 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:20926 https://access.redhat.com/errata/RHSA-2025:20926
Comment 10 errata-xmlrpc 2025-11-11 14:59:50 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:20955 https://access.redhat.com/errata/RHSA-2025:20955
Comment 11 errata-xmlrpc 2025-11-24 01:59:05 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:21916 https://access.redhat.com/errata/RHSA-2025:21916
Comment 12 errata-xmlrpc 2025-11-24 09:41:34 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:21936 https://access.redhat.com/errata/RHSA-2025:21936
Note You need to log in before you can comment on or make changes to this bug.