CVE-2026-97057
Description
A flaw was found in redis-parser. This vulnerability allows a malicious or compromised Redis endpoint to trigger an uncaught RangeError by sending a crafted RESP (REdis Serialization Protocol) header with an excessively large declared length. The flaw occurs because redis-parser fails to validate the multi-bulk length value during RESP protocol parsing. Successful exploitation can lead to a Denial of Service (DoS) by crashing the Node.js client process.
Statement
An Important-impact denial-of-service flaw was found in redis-parser, a Node.js library that parses the Redis RESP protocol. redis-parser does not validate the multi-bulk (array) length value during RESP protocol parsing, so a malicious or compromised Redis endpoint can send a crafted RESP header declaring an excessively large length (above 2^32-1), which triggers an uncaught RangeError and crashes the Node.js client process that connected to it. Only the availability of the client process is impacted; there is no impact to confidentiality or integrity. Red Hat rates this flaw Important with a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), slightly lower than the 8.7 CVSS 4.0 score in the upstream CVE.org record, although both ratings correspond to Important severity.
The redis-parser library is bundled as a dependency in Red Hat Ansible Automation Platform (automation-portal containers), Red Hat Satellite, and Red Hat Insights remediations components; these products are tracked as affected and a fix is being pursued by the responsible product teams. Other Red Hat offerings that bundle redis-parser, including Red Hat Developer Hub, Red Hat JBoss Fuse, and the cloudservices remediations container, have been assessed as not affected because the vulnerable code is not in an executed path or the component is not present in those products.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | 7.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality,Integrity
Technical Impact: Read Memory; Modify Memory; Varies by Context
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.