# CVE-2025-48367: Redis DoS Vulnerability due to bad connection error handling

> An unauthenticated attacker can cause a denial of service in Redis by triggering repeated IP protocol errors, leading to client starvation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 7 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** ALPINE-CVE-2025-48367, AZL-64809, AZL-64827, BELL-CVE-2025-48367, BIT-keydb-2025-48367, BIT-redis-2025-48367, BIT-valkey-2025-48367, CLSA-2025-1755886747, DEBIAN-CVE-2025-48367, ECHO-f51e-2328-f2bb, GHSA-4q32-c38c-pwgq, MINI-57cw-52gg-jjrf, MINI-6r8r-9685-cmc6, MINI-h72v-r338-qf54, MINI-m8ww-4mmc-mfv4, UBUNTU-CVE-2025-48367

## What is CVE-2025-48367?

CVE-2025-48367 is a high-severity denial of service vulnerability in redis, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Redis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-48367?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | Bitnami | All versions | 6.2.19, 7.2.10, 8.0.3, 7.4.5 |
| `keydb` | Bitnami | All versions | 6.2.19, 7.2.10, 8.0.3, 7.4.5 |
| `valkey` | Bitnami | All versions | 7.2.10, 8.0.4, 8.1.3 |

Products: Redis Redis.

## How do I fix CVE-2025-48367?

Upgrade redis to a fixed version for your release line: 6.2.19, 7.2.10, 8.0.3 or 7.4.5.

## Is CVE-2025-48367 being exploited?

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

## Other vulnerabilities in redis

- [CVE-2022-0543](https://insights.sbomify.com/CVE-2022-0543/): Debian-specific Redis Server Lua Sandbox Escape (critical 10.0, exploited in the wild)
- [CVE-2026-23479](https://insights.sbomify.com/CVE-2026-23479/): redis-server use-after-free in unblock client flow may allow remote code execution (high 7.7)
- [CVE-2026-25243](https://insights.sbomify.com/CVE-2026-25243/): redis-server RESTORE invalid memory access may allow remote code execution (high 7.7)
- [CVE-2025-62507](https://insights.sbomify.com/CVE-2025-62507/): Redis: Bug in XACKDEL may lead to stack overflow and potential RCE (high 7.7)
- [CVE-2023-31655](https://insights.sbomify.com/CVE-2023-31655/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48367 and fix it if it is affected.

What it is: CVE-2025-48367 is a high-severity denial of service vulnerability in redis, published on 7 Jul 2025. 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-2025-48367 in the wild and no public exploit code.

Affected packages and fixed versions:
- redis (Bitnami): affected all versions; fixed in 6.2.19, 7.2.10, 8.0.3, 7.4.5
- keydb (Bitnami): affected all versions; fixed in 6.2.19, 7.2.10, 8.0.3, 7.4.5
- valkey (Bitnami): affected all versions; fixed in 7.2.10, 8.0.4, 8.1.3

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-2025-48367/ (Markdown: https://insights.sbomify.com/CVE-2025-48367/index.md)
```

## Sources

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

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