GitHub Advisoryadvisory · npm
GHSA-2h8j-8r9p-849f @digitalocean/do-markdownit has Type Confusion vulnerability
MEDIUM
Official page ↗
- Aliases
- CVE-2025-59717
- Ecosystem
- npm
- Packages
- @digitalocean/do-markdownit
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- Weaknesses
- CWE-843
- Reviewed
- 2025-09-19
Affected packages
• npm @digitalocean/do-markdownit: <= 1.16.1 (no fix yet)
Description
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.
Affected Versions
All versions up to and including 1.16.1 (npm).
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.
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.
Related
Alias · CVE (1)
- CVE-2025-59717 In the @digitalocean/do-markdownit package through 1.16.1 (in npm), the callout and fence_environment plugins perform .includes substring… vulnerability
Weakness · CWE (1)
- CWE-843 Access of Resource Using Incompatible Type weakness