markdownlint-0.30.123.tgz: 2 vulnerabilities (highest severity is: 5.3) - autoclosed

[mend-bolt-for-github]

Vulnerable Library - markdownlint-0.30.123.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Found in HEAD commit: f8c95293185f34b92585cb3cc1006d71a4c00395

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (markdownlint version)	Remediation Possible**
CVE-2026-2327	Medium	5.3	markdown-it-14.1.0.tgz	Transitive	N/A*	❌
CVE-2025-64718	Medium	5.3	js-yaml-4.1.0.tgz	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-2327

Vulnerable Library - markdown-it-14.1.0.tgz

Library home page: https://registry.npmjs.org/markdown-it/-/markdown-it-14.1.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• markdownlint-0.30.123.tgz (Root Library)
  • markdownlint-cli2-0.17.2.tgz
    • markdownlint-0.37.4.tgz
      • ❌ markdown-it-14.1.0.tgz (Vulnerable Library)

Found in HEAD commit: f8c95293185f34b92585cb3cc1006d71a4c00395

Found in base branch: main

Vulnerability Details

Versions of the package markdown-it from 13.0.0 and before 14.1.1 are vulnerable to Regular Expression Denial of Service (ReDoS) due to the use of the regex /*+$/ in the linkify function. An attacker can supply a long sequence of * characters followed by a non-matching character, which triggers excessive backtracking and may lead to a denial-of-service condition.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2026-02-12

URL: CVE-2026-2327

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-02-12

Fix Resolution: markdown-it - 14.1.1,https://github.com/markdown-it/markdown-it.git - 14.1.1

Step up your Open Source Security Game with Mend here

CVE-2025-64718

Vulnerable Library - js-yaml-4.1.0.tgz

YAML 1.2 parser and serializer

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• markdownlint-0.30.123.tgz (Root Library)
  • markdownlint-cli2-0.17.2.tgz
    • ❌ js-yaml-4.1.0.tgz (Vulnerable Library)

Found in HEAD commit: f8c95293185f34b92585cb3cc1006d71a4c00395

Found in base branch: main

Vulnerability Details

js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution ("proto"). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using "node --disable-proto=delete" or "deno" (in Deno, pollution protection is on by default).

Publish Date: 2025-11-13

URL: CVE-2025-64718

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-mh29-5h37-fv8m

Release Date: 2025-11-13

Fix Resolution: js-yaml - 4.1.1,js-yaml - 3.14.2

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.