CVE-2025-48367VulnerabilityPublished 16 Oct 2025Updated 8 Sep 2026

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

Affects valkeySource GCVE Database

Not known to be exploited · fixed in 8.1.3 : patch valkey soon.

Data as of 26 Oct 2026, 06:15 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.1.3, 8.0.4, 7.2.10

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade valkey to 8.1.3, 8.0.4 or 7.2.10.

Patches and advisories

github.com/redis/redis/commit/bde62951accfc4bb0a516276fd0b4b307e140ce2 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Bitnamivalkey`pkg:bitnami/valkey`Other threats	Affected <7.2.10 >=7.3.0 <8.0.4 >=8.1.0 <8.1.3	Fixed in 7.2.10 8.0.4 8.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading to Redis versions 8.0.3, 7.4.5, 7.2.10, or 6.2.19 or later. Refer to the official Redis GitHub commit (https://github.com/redis/redis/commit/bde62951accfc4bb0a516276fd0b4b307e140ce2) for details. No additional mitigation is indicated by the vendor advisory.

Description

CVE-2025-48367 is a denial of service vulnerability in Redis caused by improper handling of connection errors. An unauthenticated connection can trigger repeated IP protocol errors, resulting in client starvation and service disruption. The issue affects multiple Redis versions and has been fixed in versions 8.0.3, 7.4.5, 7.2.10, and 6.2.19.

Impact

Exploitation of this vulnerability can cause denial of service by exhausting client connections through repeated IP protocol errors. This disrupts normal Redis operations and availability. No authenticated access is required to trigger the issue, increasing the risk surface.

Summary

Redis, an open source in-memory database, contains a vulnerability (CVE-2025-48367) where unauthenticated connections can cause repeated IP protocol errors. This leads to client starvation and ultimately a denial of service condition. The vulnerability is addressed by patches released in Redis versions 8.0.3, 7.4.5, 7.2.10, and 6.2.19. A fix is available as per the linked GitHub commit.

References

Community reviews

Loading reviews…