https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 04:18:39 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-253096 EUVD-2026-253096 https://cve.radiocsirt.org/vuln/euvd-2026-253096 https://cve.radiocsirt.org/vuln/fkie_cve-2025-59717 <p>In the @digitalocean/do-markdownit package through 1.16.1 (in npm), the callout and fence_environment plugins perform .includes substring matching if allowedClasses or allowedEnvironments is a string (instead of an array).</p> <p>In the @digitalocean/do-markdownit package through 1.16.1 (in npm), the callout and fence_environment plugins perform .includes substring matching if allowedClasses or allowedEnvironments is a string (instead of an array).</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-59717 https://cve.radiocsirt.org/vuln/ghsa-2h8j-8r9p-849f <p><strong>Affected:</strong> npm: @digitalocean/do-markdownit</p> <p>### Overview A type confusion issue exists in the `@digitalocean/do-markdownit` package. In the `callout` and `fence_environment` plugins, the `allowedClasses` and `allowedEnvironments` options are expected to be arrays of strings. If these options are provided as a single string, the code applies `.includes` directly on the string, resulting in substring matching instead of membership checks against an array.</p> <p>### Affected Versions All versions up to and including 1.16.1 (npm).</p> <p>### Impact Supplying crafted input can bypass intended allow-lists (e.g., class/environment constraints) due to substring checks, which may enable rendering of unintended classes or environments and lead to policy bypass in downstream consumers.</p> <p>### Mitigation Until an upstream fix is released, ensure configuration normalization before invoking the plugins: - Validate that `allowedClasses` and `allowedEnvironments` are arrays (`Array.isArray(...)`), converting single strings into one-element arrays when necessary. - Consider sanitizing or strictly validating user-controlled values that influence Markdown rendering.</p> <p><strong>Affected:</strong> npm: @digitalocean/do-markdownit</p> <p>### Overview A type confusion issue exists in the `@digitalocean/do-markdownit` package. In the `callout` and `fence_environment` plugins, the `allowedClasses` and `allowedEnvironments` options are expected to be arrays of strings. If these options are provided as a single string, the code applies `.includes` directly on the string, resulting in substring matching instead of membership checks against an array.</p> <p>### Affected Versions All versions up to and including 1.16.1 (npm).</p> <p>### Impact Supplying crafted input can bypass intended allow-lists (e.g., class/environment constraints) due to substring checks, which may enable rendering of unintended classes or environments and lead to policy bypass in downstream consumers.</p> <p>### Mitigation Until an upstream fix is released, ensure configuration normalization before invoking the plugins: - Validate that `allowedClasses` and `allowedEnvironments` are arrays (`Array.isArray(...)`), converting single strings into one-element arrays when necessary. - Consider sanitizing or strictly validating user-controlled values that influence Markdown rendering.</p> https://cve.radiocsirt.org/vuln/ghsa-2h8j-8r9p-849f