Skip to content
Applications

CVE-2026-84372

9.8
Critical
EPSS 0.41%Patch availableSep 2, 2026

CRLF injection in Predis pipeline allows injected Redis commands and disruption.

common questions

Is CVE-2026-84372 being exploited?

Not confirmed. CVE-2026-84372 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-84372?

CVE-2026-84372 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-84372?

Yes. A fix has been recorded for CVE-2026-84372. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84372 affect?

CVE-2026-84372 affects Predis PHP client v3.0.0-RC1 through v3.3.0, PHP apps using Predis pipeline() on Redis clusters/replicas, Redis clusters/replicas accessed by Predis. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84372?

Upgrade Predis to v3.3.0 and avoid pipeline() with untrusted input.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Predis PHP client v3.0.0-RC1 through v3.3.0PHP apps using Predis pipeline() on Redis clusters/replicasRedis clusters/replicas accessed by Predis
impact

CRLF in keys/values during pipeline parsing allows injection of Redis commands: shard-wide deletes, data reads/modification, or node disruption; replication may crash requests.

action required

Immediate action required

affected versions
predis predis
  • affected>= 3.0.0-RC1 and < 3.3.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free