CVE-2026-14699

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory published 2026-07-05. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A weakness has been identified in zcaceres markdownify-mcp up to 1.1.0. The affected element is the function assertPathAllowed of the file src/Markdownify.ts. Executing a manipulation can lead to symlink following. The attack can only be executed locally. The pull request to fix this issue awaits acceptance.

CVSS v3
3.3
EG Score
3.3(medium)
EG Risk
15(Track)
EG Risk 15/100SSVC: Track

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
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 5, 2026

Last Modified

July 6, 2026

References (7)

Vendor Advisories for CVE-2026-14699(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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.

  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-23 04:15 UTCEG score recompute
  3. 2026-08-23 04:15 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 03:03 UTCEG score recompute
  8. 2026-08-20 03:02 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 21:25 UTCEG score recompute
  13. 2026-08-16 21:25 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 20:12 UTCEG score recompute
  19. 2026-08-13 20:12 UTCGHSA enrichment
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-11 13:42 UTCEPSS rescore
  22. 2026-08-10 23:59 UTCEPSS rescore
  23. 2026-08-10 19:00 UTCEG score recompute
  24. 2026-08-10 19:00 UTCGHSA enrichment
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 51 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-07 17:48 UTCEG score recompute
  3. 2026-08-07 17:48 UTCGHSA enrichment
  4. 2026-08-06 13:46 UTCEPSS rescore
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-04 16:36 UTCEG score recompute
  7. 2026-08-04 16:36 UTCGHSA enrichment
  8. 2026-08-04 15:09 UTCEPSS rescore
  9. 2026-08-04 10:38 UTCEPSS rescore
  10. 2026-08-03 10:35 UTCEPSS rescore
  11. 2026-08-02 02:26 UTCEPSS rescore
  12. 2026-08-01 15:18 UTCEG score recompute
  13. 2026-08-01 15:18 UTCGHSA enrichment
  14. 2026-08-01 04:15 UTCEPSS rescore
  15. 2026-07-30 16:27 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-29 14:05 UTCEG score recompute
  18. 2026-07-29 14:05 UTCGHSA enrichment
  19. 2026-07-28 15:36 UTCEPSS rescore
  20. 2026-07-27 14:13 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 12:52 UTCEG score recompute
  24. 2026-07-26 12:52 UTCGHSA enrichment
  25. 2026-07-25 14:17 UTCEPSS rescore
  26. 2026-07-24 14:17 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 03:05 UTCEG score recompute
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:24 UTCEPSS rescore
  31. 2026-07-20 17:08 UTCEPSS rescore
  32. 2026-07-19 14:30 UTCEPSS rescore
  33. 2026-07-18 10:04 UTCEPSS rescore
  34. 2026-07-16 17:02 UTCEPSS rescore
  35. 2026-07-15 16:57 UTCEPSS rescore
  36. 2026-07-15 02:00 UTCEPSS rescore
  37. 2026-07-14 08:04 UTCGHSA enrichment
  38. 2026-07-13 22:30 UTCEPSS rescore
  39. 2026-07-13 06:12 UTCEPSS rescore
  40. 2026-07-12 05:46 UTCEPSS rescore
  41. 2026-07-11 08:27 UTCEPSS rescore
  42. 2026-07-11 06:52 UTCGHSA enrichment
  43. 2026-07-09 19:10 UTCEPSS rescore
  44. 2026-07-08 15:15 UTCEPSS rescore
  45. 2026-07-08 15:15 UTCEPSS rescore
  46. 2026-07-08 05:39 UTCGHSA enrichment
  47. 2026-07-07 13:46 UTCEPSS rescore
  48. 2026-07-06 16:27 UTCEPSS rescore
  49. 2026-07-06 02:23 UTCEPSS rescore
  50. 2026-07-05 04:25 UTCEG score recompute
  51. 2026-07-05 04:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14699?
CVE-2026-14699 is a low vulnerability published on July 5, 2026. A weakness has been identified in zcaceres markdownify-mcp up to 1.1.0. The affected element is the function assertPathAllowed of the file src/Markdownify.ts. Executing a manipulation can lead to symlink following. The attack can only be executed locally. The pull request to fix this issue awaits…
When was CVE-2026-14699 disclosed?
CVE-2026-14699 was first published in the National Vulnerability Database on July 5, 2026, with the most recent update on July 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-14699 actively exploited?
CVE-2026-14699 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 93.2% of all scored CVEs.
What is the CVSS score of CVE-2026-14699?
CVE-2026-14699 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-14699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14699, 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

Explore the affected products and dependency analysis for CVE-2026-14699

Explore →

Is Your Infrastructure Affected by CVE-2026-14699?

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

Start Free Scan →Browse All CVEs