Denial of Service Vulnerability in redis-parser via RESP Protocol
The redis-parser library up to version 3.0.0 fails to validate multi-bulk length values in the RESP protocol, allowing an attacker-controlled Redis endpoint to trigger an unhandled RangeError and crash the Node.js application process.
CVE search metadata
CVE search record: CVE-2026-97057. Severity: high. CVSS: 7.5. KEV: no. Product: redis-parser (<= 3.0.0). Brief: Denial of Service Vulnerability in redis-parser via RESP Protocol. Brief link: https://feed.craftedsignal.io/briefs/2026-09-redis-parser-dos/
Triage facts
Revision 1- Applicability
- redis-parser (<= 3.0.0)
- Evidence
- Unknown
- Severity
- Low
- Action
- Elevated
- Sources
- 1 public source
- Freshness
- Revision 1Sep 24, 14:47 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A1Likely
The redis-parser library, a component frequently used in Node.js applications for parsing the Redis Serialization Protocol (RESP), contains a critical validation flaw identified as CVE-2026-97057. The vulnerability exists because the library does not properly validate the multi-bulk length value during protocol parsing. An attacker who has compromised a Redis endpoint or is positioned as a malicious upstream Redis server can transmit a crafted RESP header with a length parameter exceeding 2^32-1. This payload causes the parser to trigger an uncaught RangeError within the JavaScript runtime, leading to an immediate process crash and denial of service. Because redis-parser is often a core dependency for Redis clients, this vulnerability directly impacts the availability of any Node.js service connecting to an untrusted or compromised Redis instance.
Impact
The vulnerability results in an application-level denial of service for any Node.js process relying on redis-parser versions 3.0.0 or earlier. By forcing a process crash, attackers can disrupt backend services, queue consumers, or data caches that rely on Redis connectivity. Given the commonality of the redis-parser library in the Node.js ecosystem, widespread availability impact is possible for services integrated with external Redis clusters or Redis instances exposed to potentially malicious input.
Recommendation
- Audit dependencies to identify all projects utilizing redis-parser versions 3.0.0 or lower.
- Upgrade to a patched version of redis-parser that implements strict bounds checking on RESP length fields as soon as the vendor provides a resolution.
- If immediate patching is not possible, implement ingress filtering or application-level sanity checks on the maximum expected size of RESP messages before passing them to the parser.
- Ensure Redis clients are configured to connect only to authenticated and trusted Redis instances to mitigate the threat of a malicious or compromised upstream server.
Immediate actions
Inventory all applications using redis-parser and assess exposure to untrusted Redis endpoints
Mitigations
Identify and upgrade to patched version of redis-parser when released
CVE-2026-97057