https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:05:18 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01717 bdu:2026-01717 https://cve.radiocsirt.org/vuln/bdu:2026-01717 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/cleanstart-2026-id18571 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: npm</p> <p>Multiple security vulnerabilities affect the npm package. brace-expansion through 5. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: npm</p> <p>Multiple security vulnerabilities affect the npm package. brace-expansion through 5. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-id18571 https://cve.radiocsirt.org/vuln/euvd-2026-337472 EUVD-2026-337472 https://cve.radiocsirt.org/vuln/euvd-2026-337472 https://cve.radiocsirt.org/vuln/fkie_cve-2026-24001 <p>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&#39;s *patch* header (also known as its &#34;leading garbage&#34;). 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 a…</p> <p>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&#39;s *patch* header (also known as its &#34;leading garbage&#34;). 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 a…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-24001 https://cve.radiocsirt.org/vuln/ghsa-73rr-hh4g-fpgx <p><strong>Affected:</strong> npm: diff</p> <p>### Impact</p> <p>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.</p> <p>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).</p> <p>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.</p> <p>Finally, a second and lesser bug - a ReDOS - also exhibits when those same line break characters are present in a patch&#39;s *patch* header (also known as its &#34;leading garbage&#34;). A maliciously-crafted patch header of length *n* can take `parsePatch` O(*n*³) time to parse.</p> <p>### Patches</p> <p>All vulnerabilities described are fixed in v8.0.3.</p> <p>### Workarounds</p> <p>If using a version of jsdiff earlier than v8.0.3, do not attempt to parse patches that contain any of th…</p> <p><strong>Affected:</strong> npm: diff</p> <p>### Impact</p> <p>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.</p> <p>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).</p> <p>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.</p> <p>Finally, a second and lesser bug - a ReDOS - also exhibits when those same line break characters are present in a patch&#39;s *patch* header (also known as its &#34;leading garbage&#34;). A maliciously-crafted patch header of length *n* can take `parsePatch` O(*n*³) time to parse.</p> <p>### Patches</p> <p>All vulnerabilities described are fixed in v8.0.3.</p> <p>### Workarounds</p> <p>If using a version of jsdiff earlier than v8.0.3, do not attempt to parse patches that contain any of th…</p> https://cve.radiocsirt.org/vuln/ghsa-73rr-hh4g-fpgx https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-24001 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: node-diff, Ubuntu:18.04:LTS: node-diff, Ubuntu:20.04:LTS: node-diff, Ubuntu:22.04:LTS: node-diff, Ubuntu:24.04:LTS: node-diff, Ubuntu:25.10: node-diff, Ubuntu:26.04:LTS: node-diff</p> <p>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&#39;s *patch* header (also known as its &#34;leading garbage&#34;). 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 a…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: node-diff, Ubuntu:18.04:LTS: node-diff, Ubuntu:20.04:LTS: node-diff, Ubuntu:22.04:LTS: node-diff, Ubuntu:24.04:LTS: node-diff, Ubuntu:25.10: node-diff, Ubuntu:26.04:LTS: node-diff</p> <p>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&#39;s *patch* header (also known as its &#34;leading garbage&#34;). 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 a…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-24001 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0526 <p>Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Daten zu manipulieren, und um einen Denial of Service Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Daten zu manipulieren, und um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0526