VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mkdocs-include-markdown-plugin: vulnerability history, versions and safety

mkdocs-include-markdown-plugin is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 71 releases, from Sep 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mkdocs-include-markdown-plugin vulnerabilities

Vulert verdict on mkdocs-include-markdown-plugin 7.3.0 i

Updated on 23 Oct 2026

Good news: 7.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 7.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.3.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 28 packages i
  • Stars 155 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for mkdocs-include-markdown-plugin, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.3.0 15 May 2026 none Apache-2.0 — Details →
7.2.2 29 Mar 2026 none Apache-2.0 — Details →
7.2.1 25 Jan 2026 none Apache-2.0 — Details →
7.2.0 28 Sep 2025 none Apache-2.0 — Details →
7.1.8 26 Sep 2025 none Apache-2.0 — Details →
7.1.7 27 Aug 2025 M1 U1 Apache-2.0 Yes Details →
7.1.6 13 Jun 2025 M1 U1 Apache-2.0 Yes Details →
7.1.5 07 Mar 2025 M1 U1 Apache-2.0 Yes Details →
7.1.4 09 Feb 2025 M1 U1 Apache-2.0 Yes Details →
7.1.3 05 Feb 2025 M1 U1 Apache-2.0 Yes Details →
7.1.2 29 Nov 2024 M1 U1 Apache-2.0 Yes Details →
7.1.1 21 Nov 2024 M1 U1 Apache-2.0 Yes Details →
7.0.1 18 Nov 2024 M1 U1 Apache-2.0 Yes Details →
7.0.0 22 Oct 2024 M1 U1 Apache-2.0 Yes Details →
6.2.2 10 Aug 2024 M1 U1 Apache-2.0 Yes Details →
6.2.1 21 Jun 2024 M1 U1 Apache-2.0 Yes Details →
6.2.0 10 Jun 2024 M1 U1 Apache-2.0 Yes Details →
6.1.1 01 Jun 2024 M1 U1 Apache-2.0 Yes Details →
6.1.0 01 Jun 2024 M1 U1 Apache-2.0 Yes Details →
6.0.7 29 May 2024 M1 U1 Apache-2.0 Yes Details →
6.0.6 02 May 2024 M1 U1 Apache-2.0 Yes Details →
6.0.5 25 Mar 2024 M1 U1 Apache-2.0 Yes Details →
6.0.4 10 Nov 2023 M1 U1 Apache-2.0 Yes Details →
6.0.3 14 Oct 2023 M1 U1 Apache-2.0 Yes Details →
6.0.2 12 Oct 2023 M1 U1 Apache-2.0 Yes Details →
6.0.1 31 Aug 2023 M1 U1 Apache-2.0 Yes Details →
6.0.0 11 Aug 2023 M1 U1 Apache-2.0 Yes Details →
5.1.0 04 Aug 2023 M1 U1 Apache-2.0 Yes Details →
5.0.0 31 Jul 2023 M1 U1 Apache-2.0 Yes Details →
4.0.4 10 Mar 2023 M1 U1 Apache-2.0 Yes Details →
4.0.3 18 Dec 2022 M1 U1 non-standard Yes Details →
4.0.2 17 Dec 2022 M1 U1 non-standard Yes Details →
4.0.1 15 Dec 2022 M1 U1 non-standard Yes Details →
4.0.0 30 Nov 2022 M1 U1 non-standard Yes Details →
3.9.1 16 Oct 2022 M1 U1 Apache-2.0 Yes Details →
3.9.0 28 Sep 2022 M1 U1 Apache-2.0 Yes Details →
3.8.1 16 Sep 2022 M1 U1 Apache-2.0 Yes Details →
3.8.0 15 Sep 2022 M1 U1 Apache-2.0 Yes Details →
3.7.1 07 Sep 2022 M1 U1 Apache-2.0 Yes Details →
3.7.0 07 Sep 2022 M1 U1 Apache-2.0 Yes Details →
3.6.1 28 Jul 2022 M1 U1 Apache-2.0 Yes Details →
3.6.0 21 Jul 2022 M1 U1 Apache-2.0 Yes Details →
3.5.2 01 Jun 2022 M1 U1 Apache-2.0 Yes Details →
3.5.1 24 May 2022 M1 U1 Apache-2.0 Yes Details →
3.5.0 23 May 2022 M1 U1 Apache-2.0 Yes Details →
3.4.1 17 May 2022 M1 U1 Apache-2.0 Yes Details →
3.4.0 05 May 2022 M1 U1 Apache-2.0 Yes Details →
3.3.0 22 Feb 2022 M1 U1 Apache-2.0 Yes Details →
3.2.3 09 Sep 2021 M1 U1 Apache-2.0 Yes Details →
3.2.2 03 Sep 2021 M1 U1 Apache-2.0 Yes Details →
3.2.1 19 Jul 2021 M1 U1 Apache-2.0 Yes Details →
3.2.0 15 Jul 2021 M1 U1 Apache-2.0 Yes Details →
3.1.4 16 Jun 2021 M1 U1 Apache-2.0 Yes Details →
3.1.3 11 Jun 2021 M1 U1 Apache-2.0 Yes Details →
3.1.1 10 Jun 2021 M1 U1 Apache-2.0 Yes Details →
3.1.0 06 Jun 2021 M1 U1 Apache-2.0 Yes Details →
3.0.1 19 May 2021 M1 U1 Apache-2.0 Yes Details →
3.0.0 19 May 2021 M1 U1 Apache-2.0 Yes Details →
2.8.0 06 Feb 2021 M1 U1 Apache-2.0 Yes Details →
2.7.2 03 Feb 2021 M1 U1 Apache-2.0 Yes Details →
2.7.1 07 Jan 2021 M1 U1 non-standard Yes Details →
2.7.0 07 Jan 2021 M1 U1 non-standard Yes Details →
2.6.1 07 Jan 2021 M1 U1 non-standard Yes Details →
2.6.0 05 Jan 2021 M1 U1 non-standard Yes Details →
2.5.0 05 Jan 2021 M1 U1 non-standard Yes Details →
2.4.0 05 Jan 2021 M1 U1 non-standard Yes Details →
2.3.0 24 Dec 2020 M1 U1 non-standard Yes Details →
2.2.0 23 Dec 2020 M1 U1 non-standard Yes Details →
2.1.2 21 Dec 2020 M1 U1 non-standard Yes Details →
2.1.1 19 Dec 2020 M1 U1 non-standard Yes Details →
2.1.0 18 Dec 2020 M1 U1 non-standard Yes Details →
2.0.0 15 Dec 2020 M1 U1 non-standard Yes Details →
1.0.0 04 Dec 2020 M1 U1 non-standard Yes Details →
0.1.0 04 Dec 2020 M1 U1 non-standard Yes Details →
0.0.2 04 Dec 2020 M1 U1 non-standard Yes Details →
0.0.1 04 Dec 2020 M1 U1 non-standard Yes Details →

All 76 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mkdocs-include-markdown-plugin

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-59940: mkdocs-include-markdown-plugin Vulnerable to Unvalidated Input Collisions 6.5 medium 7.1.8 29 Sep 2025
CVE-2025-59940: mkdocs-include-markdown-plugin Vulnerable to Unvalidated Input Collisions 6.5 medium 7.1.8 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mkdocs-include-markdown-plugin

Is mkdocs-include-markdown-plugin safe to use?

Vulert records 2 vulnerabilities for mkdocs-include-markdown-plugin in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is mkdocs-include-markdown-plugin's Vulert package health score?

Vulert scores mkdocs-include-markdown-plugin 72/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of mkdocs-include-markdown-plugin affected?

No. 7.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of mkdocs-include-markdown-plugin should I use?

7.3.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mkdocs-include-markdown-plugin have?

2 vulnerabilities are recorded for mkdocs-include-markdown-plugin in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mkdocs-include-markdown-plugin vulnerabilities disclosed?

1 vulnerability was recorded for mkdocs-include-markdown-plugin in the last 12 months, and the oldest entry in this database dates to 29 Sep 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mkdocs-include-markdown-plugin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mkdocs-include-markdown-plugin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mkdocs-include-markdown-plugin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.