Vulnerability Database · Packagist · Package report

league/commonmark: vulnerability history, versions and safety

league/commonmark is a package in the Packagist ecosystem. Vulert records 18 vulnerabilities for it across 120 releases, from Sep 2019 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded H10 M8
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
14 in the last 12 months

Most recent disclosure 30 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on league/commonmark i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 30 Sep 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 18 vulnerabilities on record across 7 years, 14 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 18 over 7 years · 14 in the last year i
  • Latest disclosure 30 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i

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 holds for league/commonmark, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.10.1 H1 M1 Yes Details →
2.10.0 H1 M1 Yes Details →
2.9.2 H2 M1 Yes Details →
2.9.1 H2 M1 Yes Details →
2.9.0 H5 M1 Yes Details →
2.8.3 H9 M3 Yes Details →
2.8.2 H9 M3 Yes Details →
2.8.1 H9 M4 Yes Details →
2.8.0 H9 M5 Yes Details →
2.7.1 H9 M5 Yes Details →
2.7.0 H9 M5 Yes Details →
2.6.2 H8 M6 Yes Details →
2.6.1 H8 M6 Yes Details →
2.6.0 H8 M6 Yes Details →
2.5.3 H9 M6 Yes Details →
2.5.2 H9 M6 Yes Details →
2.5.1 H9 M6 Yes Details →
2.5.0 H9 M6 Yes Details →
2.4.4 H9 M6 Yes Details →
2.4.3 H9 M6 Yes Details →
2.4.2 H9 M6 Yes Details →
2.4.1 H9 M6 Yes Details →
2.4.0 H9 M6 Yes Details →
2.3.9 H9 M6 Yes Details →
2.3.8 H9 M6 Yes Details →
2.3.7 H9 M6 Yes Details →
2.3.6 H9 M6 Yes Details →
2.3.5 H9 M6 Yes Details →
2.3.4 H9 M6 Yes Details →
2.3.3 H9 M6 Yes Details →
2.3.2 H9 M6 Yes Details →
2.3.1 H9 M6 Yes Details →
2.3.0 H9 M6 Yes Details →
2.2.5 H9 M6 Yes Details →
2.2.4 H9 M6 Yes Details →
2.2.3 H9 M6 Yes Details →
2.2.2 H9 M6 Yes Details →
2.2.1 H9 M6 Yes Details →
2.2.0 H9 M6 Yes Details →
2.1.3 H9 M6 Yes Details →
2.1.2 H9 M6 Yes Details →
2.1.1 H9 M6 Yes Details →
2.1.0 H9 M6 Yes Details →
2.0.4 H9 M6 Yes Details →
2.0.3 H9 M6 Yes Details →
2.0.2 H9 M6 Yes Details →
2.0.1 H9 M6 Yes Details →
2.0.0 H9 M6 Yes Details →
2.0.0-rc2 H7 M5 Yes Details →
2.0.0-rc1 H7 M5 Yes Details →
2.0.0-beta3 H7 M5 Yes Details →
2.0.0-beta2 H7 M5 Yes Details →
2.0.0-beta1 H7 M5 Yes Details →
1.6.7 H7 M5 Yes Details →
1.6.6 H7 M5 Yes Details →
1.6.5 H7 M5 Yes Details →
1.6.4 H7 M5 Yes Details →
1.6.3 H7 M5 Yes Details →
1.6.2 H7 M5 Yes Details →
1.6.1 H7 M5 Yes Details →
1.6.0 H7 M5 Yes Details →
1.5.8 H7 M5 Yes Details →
1.5.7 H7 M5 Yes Details →
1.5.6 H7 M5 Yes Details →
1.5.5 H7 M5 Yes Details →
1.5.4 H7 M5 Yes Details →
1.5.3 H7 M5 Yes Details →
1.5.2 H7 M5 Yes Details →
1.5.1 H7 M5 Yes Details →
1.5.0 H7 M5 Yes Details →
1.4.3 H3 M4 Yes Details →
1.4.2 H3 M4 Yes Details →
1.4.1 H3 M4 Yes Details →
1.4.0 H3 M4 Yes Details →
1.3.4 H3 M4 Yes Details →
1.3.3 H3 M4 Yes Details →
1.3.2 H3 M4 Yes Details →
1.3.1 H3 M4 Yes Details →
1.3.0 H3 M4 Yes Details →
1.2.2 H3 M3 Yes Details →
1.2.1 H3 M3 Yes Details →
1.2.0 H3 M3 Yes Details →
1.1.3 H3 M3 Yes Details →
1.1.2 H3 M3 Yes Details →
1.1.1 H3 M3 Yes Details →
1.1.0 H3 M3 Yes Details →
1.0.0 H3 M3 Yes Details →
1.0.0-rc1 H3 M3 Yes Details →
1.0.0-beta4 H3 M3 Yes Details →
1.0.0-beta3 H3 M3 Yes Details →
1.0.0-beta2 H3 M3 Yes Details →
1.0.0-beta1 H3 M3 Yes Details →
0.19.3 H3 M3 Yes Details →
0.19.2 H3 M3 Yes Details →
0.19.1 H3 M3 Yes Details →
0.19.0 H3 M3 Yes Details →
0.18.5 H3 M3 Yes Details →
0.18.4 H3 M3 Yes Details →
0.18.3 H3 M3 Yes Details →
0.18.2 H3 M4 Yes Details →
0.18.1 H3 M4 Yes Details →
0.18.0 H3 M5 Yes Details →
0.17.5 H3 M5 Yes Details →
0.17.4 H3 M5 Yes Details →
0.17.3 H3 M5 Yes Details →
0.17.2 H3 M5 Yes Details →
0.17.1 H3 M5 Yes Details →
0.17.0 H3 M5 Yes Details →
0.16.0 H3 M5 Yes Details →
0.15.7 H3 M5 Yes Details →
0.15.6 H3 M5 Yes Details →
0.15.5 H3 M4 Yes Details →
0.15.4 H3 M4 Yes Details →
0.15.3 H3 M4 Yes Details →
0.15.2 H3 M4 Yes Details →
0.15.1 H3 M4 Yes Details →
0.15.0 H3 M4 Yes Details →
0.14.0 H3 M4 Yes Details →
0.13.4 H3 M4 Yes Details →
0.13.3 H3 M4 Yes Details →

Newest 120 of 145 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2022 1
  • 2024 1
  • 2025 1
  • 2026 14

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

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 league/commonmark

Is league/commonmark safe to use?

Vulert records 18 vulnerabilities for league/commonmark in Packagist: 0 critical, 10 high, 8 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does league/commonmark have?

18 vulnerabilities are recorded for league/commonmark in the Packagist ecosystem: 0 critical, 10 high, 8 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new league/commonmark vulnerabilities disclosed?

14 vulnerabilities were recorded for league/commonmark in the last 12 months, and the oldest entry in this database dates to 17 Sep 2019. 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 league/commonmark 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 league/commonmark for upcoming vulnerabilities?

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