https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:28:40 +0000 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0923 certfr-2024-avi-0923 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0923 https://cve.radiocsirt.org/vuln/cleanstart-2026-dg43720 <p><strong>Affected:</strong> CleanStart: argo-workflows</p> <p>CVE-2024-45296 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: argo-workflows</p> <p>CVE-2024-45296 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-dg43720 https://cve.radiocsirt.org/vuln/euvd-2026-211839 EUVD-2026-211839 https://cve.radiocsirt.org/vuln/euvd-2026-211839 https://cve.radiocsirt.org/vuln/fkie_cve-2024-45296 <p>path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.</p> <p>path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-45296 https://cve.radiocsirt.org/vuln/ghsa-9wv6-86v2-598j <p><strong>Affected:</strong> npm: path-to-regexp</p> <p>### Impact</p> <p>A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (`.`). For example, `/:a-:b`.</p> <p>### Patches</p> <p>For users of 0.1, upgrade to `0.1.10`. All other users should upgrade to `8.0.0`.</p> <p>These versions add backtrack protection when a custom regex pattern is not provided:</p> <p>- [0.1.10](https://github.com/pillarjs/path-to-regexp/releases/tag/v0.1.10) - [1.9.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v1.9.0) - [3.3.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v3.3.0) - [6.3.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v6.3.0)</p> <p>They do not protect against vulnerable user supplied capture groups. Protecting against explicit user patterns is out of scope for old versions and not considered a vulnerability.</p> <p>Version [7.1.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v7.1.0) can enable `strict: true` and get an error when the regular expression might be bad.</p> <p>Version [8.0.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v8.0.0) removes the features that can cause a ReDoS.</p> <p>### Workarounds</p> <p>All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change `/:a-:b` to `/:a-:b([^-/]+)`.</p> <p>If paths cannot be rewritten and versions cannot be upgraded, anothe…</p> <p><strong>Affected:</strong> npm: path-to-regexp</p> <p>### Impact</p> <p>A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (`.`). For example, `/:a-:b`.</p> <p>### Patches</p> <p>For users of 0.1, upgrade to `0.1.10`. All other users should upgrade to `8.0.0`.</p> <p>These versions add backtrack protection when a custom regex pattern is not provided:</p> <p>- [0.1.10](https://github.com/pillarjs/path-to-regexp/releases/tag/v0.1.10) - [1.9.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v1.9.0) - [3.3.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v3.3.0) - [6.3.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v6.3.0)</p> <p>They do not protect against vulnerable user supplied capture groups. Protecting against explicit user patterns is out of scope for old versions and not considered a vulnerability.</p> <p>Version [7.1.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v7.1.0) can enable `strict: true` and get an error when the regular expression might be bad.</p> <p>Version [8.0.0](https://github.com/pillarjs/path-to-regexp/releases/tag/v8.0.0) removes the features that can cause a ReDoS.</p> <p>### Workarounds</p> <p>All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change `/:a-:b` to `/:a-:b([^-/]+)`.</p> <p>If paths cannot be rewritten and versions cannot be upgraded, anothe…</p> https://cve.radiocsirt.org/vuln/ghsa-9wv6-86v2-598j https://cve.radiocsirt.org/vuln/msrc_cve-2024-45296 msrc_CVE-2024-45296 https://cve.radiocsirt.org/vuln/msrc_cve-2024-45296 https://cve.radiocsirt.org/vuln/ncsc-2026-0034 NCSC-2026-0034 https://cve.radiocsirt.org/vuln/ncsc-2026-0034 https://cve.radiocsirt.org/vuln/opensuse-su-2024:14374-1 <p>argocd-cli-2.12.4-1.1 on GA media</p> <p>argocd-cli-2.12.4-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14374-1 https://cve.radiocsirt.org/vuln/rhba-2024:11265 <p>http-proxy-middleware: http-proxy-middleware: Denial of Service via unhandled error during path matching cross-spawn: regular expression denial of service path-to-regexp: Backtracking regular expressions cause ReDoS body-parser: Denial of Service Vulnerability in body-parser plugin-catalog-backend: prototype pollution vulnerability plugin-techdocs-backend: storage bucket directory traversal in TechDocs plugin-techdocs-backend: circumvention of XSS protection in TechDocs backstage/plugin-app-backend: Unexpected visibility of environment variable configurations in @backstage/plugin-app-backend</p> <p>http-proxy-middleware: http-proxy-middleware: Denial of Service via unhandled error during path matching cross-spawn: regular expression denial of service path-to-regexp: Backtracking regular expressions cause ReDoS body-parser: Denial of Service Vulnerability in body-parser plugin-catalog-backend: prototype pollution vulnerability plugin-techdocs-backend: storage bucket directory traversal in TechDocs plugin-techdocs-backend: circumvention of XSS protection in TechDocs backstage/plugin-app-backend: Unexpected visibility of environment variable configurations in @backstage/plugin-app-backend</p> https://cve.radiocsirt.org/vuln/rhba-2024:11265 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45296 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: node-path-to-regexp, Ubuntu:Pro:18.04:LTS: node-path-to-regexp, Ubuntu:Pro:20.04:LTS: node-path-to-regexp, Ubuntu:Pro:22.04:LTS: node-path-to-regexp, Ubuntu:Pro:24.04:LTS: node-path-to-regexp, Ubuntu:25.10: node-express, Ubuntu:26.04:LTS: node-express</p> <p>path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: node-path-to-regexp, Ubuntu:Pro:18.04:LTS: node-path-to-regexp, Ubuntu:Pro:20.04:LTS: node-path-to-regexp, Ubuntu:Pro:22.04:LTS: node-path-to-regexp, Ubuntu:Pro:24.04:LTS: node-path-to-regexp, Ubuntu:25.10: node-express, Ubuntu:26.04:LTS: node-express</p> <p>path-to-regexp turns path strings into a regular expressions. In certain cases, path-to-regexp will output a regular expression that can be exploited to cause poor performance. Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and lead to a DoS. The bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-45296 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3211 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM App Connect Enterprise ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3211