Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch

CVSS 4.0 2.7 LOWEUVD CVSS 4.0 2.7 CVSS 4.0 · [email protected] · Secondary 2.7 LOWCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS 3.1 · 0b0ca135-0b70-47e7-9f44-1890c2a1c46c · Secondary 7.5 HIGHCVSS_V4 Publisher rating LOWFixed by diff 8.0.3Fixed by diff 5.2.2Fixed by diff 4.0.4Fixed by diff 3.5.1KEV status unknown

cve-program · CVE-2026-24001

Published

jsdiff is a JavaScript text differencing implementation. Prior to versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1, 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 library are unaffected. Finally, a second and lesser interdependent bug - a ReDOS - also exhibits when those same line break characters are present in a patch's *patch* header (also known as its "leading garbage"). A maliciously-crafted patch header of length *n* can take `parsePatch` O(*n*³) time to parse. Versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1 contain a fix. As a workaround, do not attempt to parse patches that contain any of these characters: `\r`, `\u2028`, or `\u2029`.

Read the publisher's advisory

euvd · EUVD-2026-2424

Published

jsdiff is a JavaScript text differencing implementation. Prior to versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1, 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 library are unaffected. Finally, a second and lesser interdependent bug - a ReDOS - also exhibits when those same line break characters are present in a patch's *patch* header (also known as its "leading garbage"). A maliciously-crafted patch header of length *n* can take `parsePatch` O(*n*³) time to parse. Versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1 contain a fix. As a workaround, do not attempt to parse patches that contain any of these characters: `\r`, `\u2028`, or `\u2029`.

Read the publisher's advisory

nvd · CVE-2026-24001

Published

jsdiff is a JavaScript text differencing implementation. Prior to versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1, 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 library are unaffected. Finally, a second and lesser interdependent bug - a ReDOS - also exhibits when those same line break characters are present in a patch's *patch* header (also known as its "leading garbage"). A maliciously-crafted patch header of length *n* can take `parsePatch` O(*n*³) time to parse. Versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1 contain a fix. As a workaround, do not attempt to parse patches that contain any of these characters: `\r`, `\u2028`, or `\u2029`.

Read the publisher's advisory

osv · GHSA-73rr-hh4g-fpgx

Published

### 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 library are unaffected. Finally, a second and lesser bug - a ReDOS - also exhibits when those same line break characters are present in a patch's *patch* header (also known as its "leading garbage"). A maliciously-crafted patch header of length *n* can take `parsePatch` O(*n*³) time to parse. ### Patches All vulnerabilities described are fixed in v8.0.3. ### Workarounds If using a version of jsdiff earlier than v8.0.3, do not attempt to parse patches that contain any of these characters: `\r`, `\u2028`, or `\u2029`. ### References PR that fixed the bug: https://github.com/kpdecker/jsdiff/pull/649 ### CVE Notes Note that although the advisory describes two bugs, they each enable exactly the same attack vector (that an attacker who controls input to `parsePatch` can cause a DOS). Fixing one bug without fixing the other therefore does not fix the vulnerability and does not provide any security benefit. Therefore we assume that the bugs cannot possibly constitute Independently Fixable Vulnerabilities in the sense of CVE CNA rule 4.2.11, but rather that this advisory is properly construed under the rules as describing a single Vulnerability.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-24001

Published

jsdiff

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "kpdecker",
                    "product": "jsdiff",
                    "versions": [
                        {
                            "version": ">= 6.0.0, < 8.0.3",
                            "status": "affected"
                        },
                        {
                            "version": ">= 5.0.0, < 5.2.2",
                            "status": "affected"
                        },
                        {
                            "version": ">= 4.0.0, < 4.0.4",
                            "status": "affected"
                        },
                        {
                            "version": "< 3.5.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-2424

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jan 22, 2026, 2:23:44 AM

dateUpdated: Jul 15, 2026, 1:17:39 AM

2 related source bulletins · separate from aliases

WID-SEC-W-2026-2933: Splunk SOAR: Mehrere Schwachstellen

CVE-2025-13465 · CVE-2025-13473 · CVE-2025-14550 · CVE-2025-15599 · CVE-2025-53859 · CVE-2025-6545 · CVE-2025-6547 · CVE-2025-66221 · CVE-2025-67724 · CVE-2025-67725 · CVE-2025-67726 · CVE-2025-68428 · CVE-2025-69873 · CVE-2026-0540 · CVE-2026-1207 · CVE-2026-1285 · CVE-2026-1287 · CVE-2026-1312 · CVE-2026-1642 · CVE-2026-2004 · CVE-2026-2005 · CVE-2026-2006 · CVE-2026-21226 · CVE-2026-21860 · CVE-2026-22702 · CVE-2026-22815 · CVE-2026-2391 · CVE-2026-24001 · CVE-2026-24040 · CVE-2026-24043 · CVE-2026-24133 · CVE-2026-24737 · CVE-2026-25535 · CVE-2026-25673 · CVE-2026-25674 · CVE-2026-25755 · CVE-2026-25940 · CVE-2026-26007 · CVE-2026-26996 · CVE-2026-27199 · CVE-2026-2739 · CVE-2026-27651 · CVE-2026-27654 · CVE-2026-27784 · CVE-2026-27959 · CVE-2026-28277 · CVE-2026-28684 · CVE-2026-28753 · CVE-2026-28755 · CVE-2026-29063 · CVE-2026-2950 · CVE-2026-30922 · CVE-2026-31898 · CVE-2026-31938 · CVE-2026-31958 · CVE-2026-32141 · CVE-2026-32597 · CVE-2026-32647 · CVE-2026-33228 · CVE-2026-33532 · CVE-2026-33671 · CVE-2026-33672 · CVE-2026-33750 · CVE-2026-34513 · CVE-2026-34514 · CVE-2026-34515 · CVE-2026-34516 · CVE-2026-34517 · CVE-2026-34518 · CVE-2026-34519 · CVE-2026-34520 · CVE-2026-34525 · CVE-2026-34601 · CVE-2026-35536 · CVE-2026-40087 · CVE-2026-40460 · CVE-2026-40701 · CVE-2026-41066 · CVE-2026-42215 · CVE-2026-42284 · CVE-2026-42934 · CVE-2026-42945 · CVE-2026-42946 · CVE-2026-44243 · CVE-2026-44244 · CVE-2026-4800 · CVE-2026-76356 · CVE-2026-76357 · CVE-2026-76358 · CVE-2026-76359 · CVE-2026-76360 · CVE-2026-76361 · CVE-2026-76362 · CVE-2026-76363 · CVE-2026-76364 · CVE-2026-76365 · CVE-2026-76366 · CVE-2026-76367 · CVE-2026-76368 · CVE-2026-76369 · CVE-2026-76370 · CVE-2026-9256

WID-SEC-W-2026-0526: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2025-61140 · CVE-2026-24001 · CVE-2026-25128 · CVE-2026-25547

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-24001

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-400 · CWE-1333

Original publisher date fields

published: 2026-01-22T03:15:47.627

lastModified: 2026-07-15T02:18:46.763

1 source CPE criteria · context only
  • cpe:2.3:a:kpdecker:jsdiff:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-73rr-hh4g-fpgx

Published

diff

npm

SEMVER · introduced 6.0.0 → fixed 8.0.3

diff

npm

SEMVER · introduced 5.0.0 → fixed 5.2.2

diff

npm

SEMVER · introduced 4.0.0 → fixed 4.0.4

diff

npm

SEMVER · introduced 0 → fixed 3.5.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current