SEPTEMBER 15, 2026
Live Feed
Back to database
Case File

CVE-2026-84372

CRITICAL · CVSS 9.8 EPSS 0.41% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-01 · Last synced 2026-09-15

CyberRota Analysis

AI-Generated

Predis versions 3.0.0-RC1 to 3.3.0 are vulnerable due to improper handling of serialized RESP buffers, allowing attackers to inject additional commands through specially crafted keys or values. The impact includes potential shard-wide cache deletion, targeted data modification, and disruption of node operations, making it critical for users of affected versions to upgrade to version 3.3.0 immediately to mitigate these risks. Organizations utilizing Predis for PHP should prioritize this vulnerability to protect their data integrity and application stability.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-84372
Severity
CRITICAL
CVSS
9.8
EPSS
0.41%

Original NVD Description

Predis is a flexible and feature-complete Redis and Valkey client for PHP. From version 3.0.0-RC1 until version 3.3.0, pipeline handling on aggregate cluster and replication connections reparses an already serialized RESP buffer in AbstractAggregateConnection::write() by splitting it with explode("\r\n") instead of honoring RESP length prefixes. Attacker-controlled keys or values containing CRLF sequences can therefore be interpreted by Command::deserializeCommand() as additional commands. On cluster connections, ClusterStrategy::getFakeKey() can route injected keyless commands using the literal fake key value "key", permitting operations such as shard-wide cache deletion, targeted data modification, data reads, or node disruption. On replication connections, malformed reparsing can throw an uncaught exception and repeatedly terminate affected requests. Only pipeline() reaches this vulnerable path; transaction() and MULTI are not affected. This issue is fixed in version 3.3.0.