CVE-2023-41053

What it is

Redis is an in-memory database that persists on disk. Redis does not correctly identify keys accessed by `SORT_RO` and as a result may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. The problem exists in Redis 7.0 or newer and has been fixed in Redis 7.0.13 and 7.2.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-09-06 21:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 06:20 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 3.3 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-09-06 21:15 UTC

Last modified

2026-06-17 06:20 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-269 · Improper privilege management

Record status

Modified

Affected

• Redis < 7.0.13
• Redis 7.2.0

Attack profile CVSS 3.1 · 3.3

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-41053.md and follow it. Check whether this project is affected by CVE-2023-41053. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge