CVE-2026-97057 json
redis-parser through 3.0.0 Denial of Service via Invalid Array Length
published last mo. modified last mo. also EUVD-2026-85883
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-97057 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-97057 updated cvss 7.5
redis-parser: redis-parser: Denial of Service via invalid RESP protocol array length
-
Red Hat Fuse 7 redis-parser 3.0.0affected: workaround, no fix planned “Will not fix”
-
Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portalaffected: workaround, no fix available
-
Red Hat Satellite 6.18 satellite/iop-remediations-rhel9 1793065138fixed: vendor fix RHSA-2026:92584
-
Red Hat Satellite 6.19 satellite/iop-remediations-rhel9 1793092253fixed: vendor fix RHSA-2026:92578
-
Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9, rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend Red Hat Self-service automation portal 2 ansible-automation-platform/bootc-automation-portal-rhel9not affected: vulnerable code not in execute path
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| npm | redis-parser | noderedis/node-redis-parser | no versions given |
Affected products
- NodeRedis redis-parser
Classification
- Weakness
-
- CWE-1284 Improper Validation of Specified Quantity in Input
References
-
github.com
/NodeRedis/node-redis-parser/issues/65
issue-tracking
-
github.com
/NodeRedis/node-redis-parser/blob/4c2d31c8717f05dea1ffd91a0e45d68f452c73bd/lib/parser.js#L212
technical-description
-
github.com
/NodeRedis/node-redis-parser/blob/4c2d31c8717f05dea1ffd91a0e45d68f452c73bd/lib/parser.js#L108-L122
technical-description
-
github.com
/NodeRedis/node-redis-parser/blob/4c2d31c8717f05dea1ffd91a0e45d68f452c73bd/lib/parser.js#L492-L550
technical-description
-
github.com
/NodeRedis/node-redis-parser/issues/47
issue-tracking
-
github.com
/NodeRedis/node-redis-parser
product
-
vulncheck.com
/advisories/redis-parser-through-3.0.0-denial-of-service-via-invalid-array-length
third-party-advisory
Sources
- CVE List CVE-2026-97057
- NVD CVE-2026-97057
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.