CVE-2026-48801

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% 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
Trending — Patch released this weekElevated
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.

linkify-it is a links recognition library with full Unicode support. Prior to 5.0.1, LinkifyIt.prototype.match, the package's primary public API, has O(N²) algorithmic complexity for inputs containing many fuzzy links or emails because the JavaScript-level scan loop re-slices input and re-runs unanchored regex searches on progressively shorter tails. Any service that synchronously renders untrusted Markdown with linkify:true on a request hot path can inherit a worker-process denial of service triggerable by a tens-of-KB request body. This issue is fixed in version 5.0.1.

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
29%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Quadratic algorithmic complexity in LinkifyIt#match scan loop · Advisory · markdown-it/linkify-it · GitHub

https://github.com/markdown-it/linkify-it/security/advisories/GHSA-22p9-wv53-3rq4
github_commit

commit 6be6d15e0641 (markdown-it/linkify-it)

Fix landed in markdown-it/linkify-it commit 6be6d15e0641 — awaiting tagged release

https://github.com/markdown-it/linkify-it/commit/6be6d15e0641bf1daeaa977d500cabc743166159

Vendor Advisories for CVE-2026-48801(10)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatopenshift4/ose-console-rhel9:17859109382026-08-11redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17860065732026-08-06redhat
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat
redhatrhdh/rhdh-hub-rhel9:17854116522026-08-03redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17853326942026-07-29redhat
redhatansible-automation-platform/automation-portal:17846229512026-07-21redhat
redhatrust-main-1.97.0-1.1.hum12026-07-11redhat

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
linkify-it—5.0.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 106× 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 128 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48801?
CVE-2026-48801 is a high vulnerability published on June 26, 2026. linkify-it is a links recognition library with full Unicode support. Prior to 5.0.1, LinkifyIt.prototype.match, the package's primary public API, has O(N²) algorithmic complexity for inputs containing many fuzzy links or emails because the JavaScript-level scan loop re-slices input and re-runs…
When was CVE-2026-48801 disclosed?
CVE-2026-48801 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48801 actively exploited?
CVE-2026-48801 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 70.7% of all scored CVEs.
What is the CVSS score of CVE-2026-48801?
CVE-2026-48801 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48801?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48801, 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-48801

Explore →

Is Your Infrastructure Affected by CVE-2026-48801?

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

Start Free Scan →Browse All CVEs