GHSA-253c-mchw-3w2r

markdown-it linkify: true has two quadratic paths, so a few hundred KB of markdown blocks the event loop for tens of seconds

Medium highest severity reported

4
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog

Catalog tools matching GHSA-253c-mchw-3w2r

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1markdown-it@8.4.2
npm
14.3.1not analyzedpackage-lock.jsonDispute
eslint-plugin-security
Static Application Security Testing (SAST) › Language-specific › JavaScript/Node.js
eslint-plugin-security-v4.2.1markdown-it@13.0.1
npm
14.3.1not analyzedpackage-lock.jsonDispute
cloudsplaining
Cloud Security
0.9.1markdown-it@14.1.1
npm
14.3.1not analyzedpackage-lock.jsonDispute
slsa-verifier
Supply Chain Compliance
v2.7.1markdown-it@14.1.0
npm
14.3.1not analyzedpackage-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-253c-mchw-3w2r · OSV GHSA-253c-mchw-3w2r

Grype data sources: https://github.com/advisories/GHSA-253c-mchw-3w2r