CVE-2025-46686 json
Multi-bulk commands sent by clients can lead to DoS
published last yr. modified 4mo ago also BIT-keydb-2025-46686 , BIT-redis-2025-46686 , BIT-valkey-2025-46686 , EUVD-2025-22464 , GHSA-2r7g-8hpc-rpq9
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami redis 8.0.4
- bitnami valkey 8.0.4
Is CVE-2025-46686 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| OSV | 3.1 | 3.5 | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | keydb | <=8.0.3 |
no fix listed |
| bitnami | redis | <8.0.4 |
8.0.4 |
| bitnami | valkey | <8.0.4 |
8.0.4 |
Affected products
- Redis Redis
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
Sources
- CVE List CVE-2025-46686
- NVD CVE-2025-46686
- OSV BIT-keydb-2025-46686
- OSV BIT-redis-2025-46686
- OSV BIT-valkey-2025-46686
- Maintainer advisory GHSA-2r7g-8hpc-rpq9
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of redis/redis published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.