Skip to content

chore(deps): update dependency markdown-it to v14.1.1 [security]#594

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-markdown-it-vulnerability
Open

chore(deps): update dependency markdown-it to v14.1.1 [security]#594
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-markdown-it-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 13, 2026

This PR contains the following updates:

Package Change Age Confidence
markdown-it 14.1.014.1.1 age confidence
markdown-it >=14.1.0>=14.1.1 age confidence

GitHub Vulnerability Alerts

CVE-2026-2327

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.


Release Notes

markdown-it/markdown-it (markdown-it)

v14.1.1

Compare Source

Security
  • Fixed regression from v13 in linkify inline rule. Specific patterns could
    cause high CPU use. Thanks to @​ltduc147 for report.

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 13, 2026
@renovate renovate bot enabled auto-merge (squash) February 13, 2026 20:34
@renovate
Copy link
Contributor Author

renovate bot commented Feb 13, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 23 workspace projects
 ERROR  Invalid Version: ^14.1.0

pnpm: Invalid Version: ^14.1.0
    at new _SemVer (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:6235:17)
    at compare (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:6646:65)
    at Object.eq (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:6730:31)
    at installSome (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:160445:223)
    at _install (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:160387:21)
    at async mutateModules (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:160247:23)
    at async recursive (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:161641:100)
    at async recursiveInstallThenUpdateWorkspaceState (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:162152:31)
    at async installDeps (/opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:161959:11)
    at async /opt/containerbase/tools/pnpm/10.29.1/24.13.1/node_modules/pnpm/dist/pnpm.cjs:195475:23

@github-actions
Copy link

❌ Failed to deploy to Netlify

Platform Status URL
Ubuntu Failed Please check the status and logs of the workflow run.
Windows Failed Please check the status and logs of the workflow run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants