What is GHSA-X6M6-5HRF-FH6R?

GHSA-X6M6-5HRF-FH6R is a high-severity uncontrolled resource consumption vulnerability in markdown-it-toc-and-anchor (npm), affecting versions < 4.2.0. It is fixed in 4.2.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-X6M6-5HRF-FH6R?

GHSA-X6M6-5HRF-FH6R has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of markdown-it-toc-and-anchor are affected by GHSA-X6M6-5HRF-FH6R?

markdown-it-toc-and-anchor (npm) versions < 4.2.0 is affected.

Is there a fix for GHSA-X6M6-5HRF-FH6R?

Yes. GHSA-X6M6-5HRF-FH6R is fixed in 4.2.0. Upgrade to this version or later.

Is GHSA-X6M6-5HRF-FH6R exploitable, and should I be worried?

Whether GHSA-X6M6-5HRF-FH6R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-X6M6-5HRF-FH6R is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-X6M6-5HRF-FH6R?

Upgrade markdown-it-toc-and-anchor to 4.2.0 or later.

GHSA-X6M6-5HRF-FH6R in markdown-it-toc-and-anchor

Q: How severe is GHSA-X6M6-5HRF-FH6R?

GHSA-X6M6-5HRF-FH6R has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of markdown-it-toc-and-anchor are affected by GHSA-X6M6-5HRF-FH6R?

markdown-it-toc-and-anchor (npm) versions < 4.2.0 is affected.

Q: Is there a fix for GHSA-X6M6-5HRF-FH6R?

Yes. GHSA-X6M6-5HRF-FH6R is fixed in 4.2.0. Upgrade to this version or later.

Q: Is GHSA-X6M6-5HRF-FH6R exploitable, and should I be worried?

Whether GHSA-X6M6-5HRF-FH6R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-X6M6-5HRF-FH6R is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-X6M6-5HRF-FH6R?

Upgrade markdown-it-toc-and-anchor to 4.2.0 or later.

Summary

Denial of Service in markdown-it-toc-and-anchor

All versions of markdown-it-toc-and-anchor are vulnerable to Denial of Service. Parsing markdown containing **text**+\n@[toc] causes the application to enter and infinite loop.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-X6M6-5HRF-FH6R has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.2.0); upgrading removes the vulnerable code path.

Affected versions

markdown-it-toc-and-anchor (< 4.2.0)

Security releases

markdown-it-toc-and-anchor → 4.2.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fix is currently available. Consider using an alternative module until a fix is made available.

Frequently Asked Questions

What is GHSA-X6M6-5HRF-FH6R? GHSA-X6M6-5HRF-FH6R is a high-severity uncontrolled resource consumption vulnerability in markdown-it-toc-and-anchor (npm), affecting versions < 4.2.0. It is fixed in 4.2.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-X6M6-5HRF-FH6R? GHSA-X6M6-5HRF-FH6R has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of markdown-it-toc-and-anchor are affected by GHSA-X6M6-5HRF-FH6R? markdown-it-toc-and-anchor (npm) versions < 4.2.0 is affected.
Is there a fix for GHSA-X6M6-5HRF-FH6R? Yes. GHSA-X6M6-5HRF-FH6R is fixed in 4.2.0. Upgrade to this version or later.
Is GHSA-X6M6-5HRF-FH6R exploitable, and should I be worried? Whether GHSA-X6M6-5HRF-FH6R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-X6M6-5HRF-FH6R is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-X6M6-5HRF-FH6R? Upgrade markdown-it-toc-and-anchor to 4.2.0 or later.