CVE-2025-59717Disclosure(digitalocean / do-markdownit)

LOWCVSS 9.8 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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).

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-843

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • do-markdownit

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Products
do-markdownit

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-03-06: 1Technical Details · 2026-03-06: 103-06
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
Full discourse1 post
  • Ali shmery@Alishmery2
    Disclosure

    Just dropped a write-up on CVE-2025-59717 While auditing "@digitalocean/do-markdownit" I found a subtle allow-list bypass caused by JavaScript’s polymorphic ".includes()" behavior. Full write-up: https://thesmartshadow.medium.com/i-was-auditing-digitalocean-do-markdownit-a-markdown-rendering-library-used-inside-a41ad702d689 #cve #cybersecurite

    Post summary

    The author released a write‑up on CVE-2025-59717, revealing an allow‑list bypass in DigitalOcean's do‑markdownit library triggered by JavaScript's .includes() polymorphism.

    00000107
    8 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appdigitaloceando-markdownit-node.js-

Explore more