CVE-2025-46686

Redis through 8.0.3 allows memory consumption via a multi-bulk command composed of many bulks, sent by an authenticated user. This occurs because the server allocates memory for the command arguments of every bulk, even when the command is skipped because of insufficient permissions. NOTE: this is disputed by the Supplier because abuse of the commands network protocol is not a violation of the Redis Security Model.

Published: 2025-07-23 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-46686 is rated Low Risk (27.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-46686

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-19 0.06% 0.17% +0.11%
2 2026-05-09 0.03% 0.06% +0.03%
3 2025-07-24 — 0.03% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-46686

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.5 3.1 LOW
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.1 1.4 [email protected]

Weakness enumeration for CVE-2025-46686

OS Trackers for CVE-2025-46686

vendor priority summary link
alpine — CVE-2025-46686: 1 source package rows (redis); 92 state rows across 4 repos (3.19-main, 3.22-community, edge-community, edge-main); fixed 0, open 92. https://security.alpinelinux.org/vuln/CVE-2025-46686
debian unimportant CVE-2025-46686 unimportant priority: Debian including 1 source packages (redis), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-46686
ubuntu medium CVE-2025-46686 medium priority: Ubuntu including 1 source packages (redis), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needed 7, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-46686

Affected software / configurations for CVE-2025-46686

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-46686

cvelogic Threat Intelligence