# CVE-2026-97057: redis-parser through 3.0.0 Denial of Service via Invalid Array Length

> Attackers can crash Node.js applications by sending crafted Redis protocol headers with invalid array lengths, causing uncaught errors.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-xwx3-3p4h-ffw8

## What is CVE-2026-97057?

CVE-2026-97057 is a high-severity denial of service vulnerability in NodeRedis redis-parser, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

redis-parser through 3.0.0 fails to validate the multi-bulk length value in RESP protocol parsing, allowing attackers to trigger an uncaught RangeError by supplying an excessively large declared length. A malicious or compromised Redis endpoint can deliver a crafted RESP header with a length above 2^32-1 to crash the Node.js client process.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2026-97057?


## How do I fix CVE-2026-97057?

No fix has been published for CVE-2026-97057 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-97057 being exploited?

There is no known exploitation of CVE-2026-97057 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97057 and fix it if it is affected.

What it is: CVE-2026-97057 is a high-severity denial of service vulnerability in NodeRedis redis-parser, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97057 in the wild and no public exploit code.

Affected product: NodeRedis redis-parser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97057/ (Markdown: https://insights.sbomify.com/CVE-2026-97057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97057
- OSV: https://osv.dev/vulnerability/CVE-2026-97057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97057/
Summaries are generated and may contain mistakes; the official description above is the record.