# CVE-2023-41056: Redis vulnerable to integer overflow in certain payloads

> Attackers can trigger an integer overflow in Redis memory buffer resizing, leading to heap overflow and potential remote code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** ALPINE-CVE-2023-41056, BELL-CVE-2023-41056, BIT-keydb-2023-41056, BIT-redis-2023-41056, BIT-valkey-2023-41056, CLEANSTART-2026-DK92825, CLSA-2026-1775836571, CLSA-2026-1776078299, DEBIAN-CVE-2023-41056, GHSA-xr47-pcmx-fq2m, RHEA-2024:1143, openSUSE-SU-2024:13572-1

## What is CVE-2023-41056?

CVE-2023-41056 is a high-severity vulnerability in Fedoraproject Fedora, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Redis is an in-memory database that persists on disk. Redis incorrectly handles resizing of memory buffers which can result in integer overflow that leads to heap overflow and potential remote code execution. This issue has been patched in version 7.0.15 and 7.2.4.

Weakness: CWE-762 (Mismatched Memory Management Routines), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-41056?

3 open source packages ship an affected version, including keydb, redis and valkey. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keydb` | Bitnami | From 7.0.9 | 7.0.15, 7.2.4 |
| `redis` | Bitnami | From 7.0.9 | 7.0.15, 7.2.4 |
| `valkey` | Bitnami | From 7.0.9 | 7.0.15, 7.2.4 |
| `redis` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.0.12-2.module+el9.3.0+21263+4e58afe8 |
| `redis-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.0.12-2.module+el9.3.0+21263+4e58afe8 |
| `redis-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.0.12-2.module+el9.3.0+21263+4e58afe8 |
| `redis-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.0.12-2.module+el9.3.0+21263+4e58afe8 |
| `redis-doc` | Red Hat:enterprise_linux:9::appstream | All versions | 0:7.0.12-2.module+el9.3.0+21263+4e58afe8 |
| `redis` | openSUSE:Tumbleweed | All versions | 7.2.4-1.1 |

Products: Fedoraproject Fedora, Redis Redis.

## How do I fix CVE-2023-41056?

Upgrade keydb to a fixed version for your release line: 7.0.15 or 7.2.4.

## Is CVE-2023-41056 being exploited?

There is no known exploitation of CVE-2023-41056 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41056 and fix it if it is affected.

What it is: CVE-2023-41056 is a high-severity vulnerability in Fedoraproject Fedora, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41056 in the wild and no public exploit code.

Affected packages and fixed versions:
- keydb (Bitnami): affected from 7.0.9; fixed in 7.0.15, 7.2.4
- redis (Bitnami): affected from 7.0.9; fixed in 7.0.15, 7.2.4
- valkey (Bitnami): affected from 7.0.9; fixed in 7.0.15, 7.2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-41056/ (Markdown: https://insights.sbomify.com/CVE-2023-41056/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-41056
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-41056
- OSV: https://osv.dev/vulnerability/CVE-2023-41056

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-41056/
Summaries are generated and may contain mistakes; the official description above is the record.