CVE-2026-7159

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.3 from GitHub Security Advisory published 2026-04-28. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was found in douinc mkdocs-mcp-plugin up to 0.4.1." No release containing a fix is confirmed on record.

A vulnerability was found in douinc mkdocs-mcp-plugin up to 0.4.1. This affects the function read_document/list_documents of the file server.py. Performing a manipulation of the argument docs_dir/file_path results in path traversal. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor confirms, that the "fix will be published within a few days."

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
64
EG Risk 64/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 27, 2026

Last Modified

April 29, 2026

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmkdocs-mcp-plugin—ghsa

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)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mkdocs-mcp-plugin0.1.0, 0.3.0, 0.4.0, 0.4.1
  • every version through 0.4.1: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 233 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-20 08:46 UTCEG score recompute
  4. 2026-10-20 08:46 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  5. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-18 03:16 UTCEG score recompute
  8. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-13 08:27 UTCEG score recompute
  14. 2026-10-13 08:27 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  15. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-10-12 15:42 UTCEG score recompute
  17. 2026-10-11 19:28 UTCEG score recompute
  18. 2026-10-11 16:43 UTCEG score recompute
  19. 2026-10-11 14:03 UTCEG score recompute
  20. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 69 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  29. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  33. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  35. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  37. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  38. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-08-17 14:01 UTCEG score recompute
  40. 2026-08-17 14:01 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  41. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-08-16 05:36 UTCEG score recompute
  44. 2026-08-16 05:36 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  45. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  46. 2026-08-15 01:40 UTCEG score recompute
  47. 2026-08-15 01:40 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  48. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-08-14 14:50 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  50. 2026-08-14 04:00 UTCEG score recompute
  51. 2026-08-14 04:00 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  52. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-08-13 04:30 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  54. 2026-08-12 17:41 UTCEG score recompute
  55. 2026-08-12 17:41 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  56. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  57. 2026-08-11 16:38 UTCEG score recompute
  58. 2026-08-11 16:38 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  59. 2026-08-11 02:00 UTCEG score recompute
  60. 2026-08-11 02:00 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  61. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-10 11:50 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  63. 2026-08-10 00:50 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  64. 2026-08-09 14:00 UTCEG score recompute
  65. 2026-08-09 14:00 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  66. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  67. 2026-08-09 03:10 UTCEG score recompute
  68. 2026-08-09 03:10 UTCGHSA enrichmentGHSA-wfr3-hf93-qgg3 · GitHub CVSS 7.3
  69. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile

Frequently asked(5)

What is CVE-2026-7159?
CVE-2026-7159 is a high-severity vulnerability; its CVE record was published on April 27, 2026. A vulnerability was found in douinc mkdocs-mcp-plugin up to 0.4.1. This affects the function readdocument/listdocuments of the file server.py. Performing a manipulation of the argument docsdir/filepath results in path traversal. The attack is possible to be carried out remotely. The exploit has…
When was the CVE record for CVE-2026-7159 published?
The CVE record for CVE-2026-7159 was published on April 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2026-7159 actively exploited?
CVE-2026-7159 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7159?
CVE-2026-7159 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-7159?
No fix for CVE-2026-7159 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was found in douinc mkdocs-mcp-plugin up to 0.4.1." No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-7159?

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