CVE-2026-41680

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Marked is a markdown parser and compiler. From 18.0.0 to 18.0.1, a critical Denial of Service (DoS) vulnerability exists in marked. By providing a specific 3-byte input sequence a tab, a vertical tab, and a newline (\x09\x0b\n)—an unauthenticated attacker can trigger an infinite recursion loop during parsing. This leads to unbounded memory allocation, causing the host Node.js application to crash via Memory Exhaustion (OOM). This vulnerability is fixed in 18.0.2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 28, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

OOM Denial of Service via Infinite Recursion in [email protected] Tokenizer · Advisory · markedjs/marked · GitHub

https://github.com/markedjs/marked/security/advisories/GHSA-6v9c-7cg6-27q7

Vendor Advisories for CVE-2026-41680(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsatellite/iop-advisor-frontend-rhel9:17811816732026-06-16redhat
redhatsatellite/iop-vulnerability-frontend-rhel9:17810324952026-06-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
marked—18.0.2—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-04 03:16 UTCOSV refresh
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 14:47 UTCEG score recompute
  5. 2026-08-17 14:47 UTCVendor advisory
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 05:46 UTCEG score recompute
  9. 2026-08-16 05:46 UTCVendor advisory
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 16:24 UTCVendor advisory
  13. 2026-08-14 04:06 UTCEG score recompute
  14. 2026-08-14 04:06 UTCVendor advisory
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 08:30 UTCVendor advisory
  17. 2026-08-12 17:47 UTCEG score recompute
  18. 2026-08-12 17:47 UTCVendor advisory
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-11 16:41 UTCEG score recompute
  21. 2026-08-11 16:41 UTCVendor advisory
  22. 2026-08-11 13:43 UTCEPSS rescore
  23. 2026-08-11 02:08 UTCEG score recompute
  24. 2026-08-11 02:08 UTCVendor advisory
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 03:54 UTCVendor advisory
  27. 2026-08-09 15:35 UTCEG score recompute
  28. 2026-08-09 15:35 UTCVendor advisory
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 03:17 UTCEG score recompute
  31. 2026-08-09 03:17 UTCVendor advisory
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 00:50 UTCEG score recompute
  34. 2026-08-08 00:50 UTCVendor advisory
  35. 2026-08-07 12:32 UTCEG score recompute
  36. 2026-08-07 12:32 UTCVendor advisory
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-06 11:22 UTCVendor advisory
  39. 2026-08-05 22:55 UTCEG score recompute
  40. 2026-08-05 22:55 UTCVendor advisory
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:38 UTCEPSS rescore
  44. 2026-08-03 21:00 UTCEG score recompute
  45. 2026-08-03 21:00 UTCVendor advisory
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-02 23:17 UTCVendor advisory
  48. 2026-08-02 10:58 UTCEG score recompute
  49. 2026-08-02 10:58 UTCVendor advisory
  50. 2026-08-02 02:27 UTCEPSS rescore
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 01:30 UTCEPSS rescore
  54. 2026-07-28 15:36 UTCEPSS rescore
  55. 2026-07-27 14:13 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-23 14:18 UTCEPSS rescore
  61. 2026-07-23 03:11 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 15:24 UTCEPSS rescore
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-20 16:34 UTCOSV refresh
  66. 2026-07-19 14:31 UTCEPSS rescore
  67. 2026-07-19 02:29 UTCEPSS rescore
  68. 2026-07-18 10:04 UTCEPSS rescore
  69. 2026-07-16 17:03 UTCEPSS rescore
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 02:00 UTCEPSS rescore
  73. 2026-07-13 22:30 UTCEPSS rescore
  74. 2026-07-13 06:13 UTCEPSS rescore
  75. 2026-07-13 06:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-41680?
CVE-2026-41680 is a high vulnerability published on April 24, 2026. Marked is a markdown parser and compiler. From 18.0.0 to 18.0.1, a critical Denial of Service (DoS) vulnerability exists in marked. By providing a specific 3-byte input sequence a tab, a vertical tab, and a newline (\x09\x0b\n)—an unauthenticated attacker can trigger an infinite recursion loop…
When was CVE-2026-41680 disclosed?
CVE-2026-41680 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41680 actively exploited?
CVE-2026-41680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.2% of all scored CVEs.
What is the CVSS score of CVE-2026-41680?
CVE-2026-41680 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41680, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41680

Explore →

Is Your Infrastructure Affected by CVE-2026-41680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs