jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch
CVE-2026-24001 · GHSA-73rr-hh4g-fpgx
- Affected
- npm diff >= 6.0.0, < 8.0.3; >= 5.0.0, < 5.2.2; >= 4.0.0, < 4.0.4; < 3.5.1
- Fixed in
- 8.0.35.2.23.5.14.0.4· Vendor fix available
- Issue
- Impact Attempting to parse a patch whose filename headers contain the line break characters \r, \u2028, or \u2029 can cause the parsePatch method to enter an infinite loop. It then consumes memory without limit until the process crashes due to running out of memory. Applications are therefore likely to be vulnerable to a denial-of-service attack if they call parsePatch with a user-provided patch as input. A large payload is not needed to trigger the vulnerability, so size limits on user input do not provide any protection. Furthermore, some applications may be vulnerable even when calling parsePatch on a patch generated by the application itself if the user is nonetheless able to control the filename headers (e.g. by directly providing the filenames of the files to be diffed). The applyPatch method is similarly affected if (and only if) called with a string representation of a patch as an argument, since under the hood it parses that string using parsePatch. Other methods of the…
Recommended action: Upgrade to 8.0.3, 5.2.2, 4.0.4 or 3.5.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.