VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

commonmarker: vulnerability history, versions and safety

commonmarker is a package in the RubyGems ecosystem. Vulert records 6 vulnerabilities for it across 120 releases, from Mar 2022 to Jan 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 M4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all commonmarker vulnerabilities

Vulert verdict on commonmarker 2.10.1 i

Updated on 23 Oct 2026

Careful: 2.10.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.10.1 — affected i
  • Vulnerabilities on record 6 over 1 year · 0 in the last year i
  • Latest disclosure 04 Jan 2024 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Stars 561 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, 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 commonmarker, 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
2.10.1 16 Oct 2026 H1 MIT No Details →
2.10.0 24 Aug 2026 H1 MIT No Details →
2.9.0 14 Jul 2026 H1 MIT No Details →
2.8.3 04 Jul 2026 H1 MIT No Details →
2.8.2 09 May 2026 H1 MIT No Details →
2.8.1 14 Apr 2026 H1 MIT No Details →
2.8.0 12 Apr 2026 H1 MIT No Details →
2.7.0 14 Mar 2026 H1 MIT No Details →
2.6.3 23 Jan 2026 H1 MIT No Details →
2.6.2 19 Jan 2026 H1 MIT No Details →
2.6.1 06 Jan 2026 H1 MIT No Details →
2.6.0 03 Dec 2025 H1 MIT No Details →
2.5.0 14 Oct 2025 H1 MIT No Details →
2.4.1 29 Sep 2025 H1 MIT No Details →
0.23.12 17 Sep 2025 H1 MIT No Details →
2.4.0 15 Sep 2025 H1 MIT No Details →
2.3.2 09 Aug 2025 H1 MIT No Details →
2.3.1 27 Jun 2025 H1 MIT No Details →
2.3.0 05 Apr 2025 H1 MIT No Details →
2.2.0 25 Mar 2025 H1 MIT No Details →
2.1.1 08 Mar 2025 H1 MIT No Details →
2.1.0 26 Feb 2025 H1 MIT No Details →
2.0.4 23 Jan 2025 H1 MIT No Details →
2.0.3 21 Jan 2025 H1 MIT No Details →
2.0.2.1 08 Jan 2025 H1 MIT No Details →
2.0.2 29 Dec 2024 H1 MIT No Details →
2.0.1 28 Nov 2024 H1 MIT No Details →
2.0.0 25 Nov 2024 H1 MIT No Details →
0.23.11 20 Nov 2024 H1 MIT No Details →
1.1.5 29 Jul 2024 H1 MIT No Details →
1.1.4 03 Jun 2024 H1 MIT No Details →
1.1.3 15 May 2024 H1 MIT No Details →
1.1.2 04 May 2024 H1 MIT No Details →
1.1.1 01 May 2024 H1 MIT No Details →
1.1.0 30 Apr 2024 H1 MIT No Details →
1.0.4 03 Jan 2024 H1 MIT No Details →
1.0.3 28 Dec 2023 H1 MIT No Details →
1.0.2 28 Dec 2023 H1 MIT No Details →
1.0.1 27 Dec 2023 H1 MIT No Details →
1.0.0 24 Dec 2023 H1 MIT No Details →
1.0.0.pre12 07 Dec 2023 H1 MIT No Details →
1.0.0.pre11 13 Nov 2023 H1 MIT No Details →
0.23.10 31 Jul 2023 H1 MIT No Details →
0.23.9 11 Apr 2023 H1 M1 MIT No Details →
1.0.0.pre8 09 Mar 2023 H1 MIT No Details →
0.23.8 31 Jan 2023 H1 M2 MIT No Details →
1.0.0.pre7 26 Jan 2023 H1 MIT No Details →
0.23.7 24 Jan 2023 H1 M2 MIT No Details →
1.0.0.pre6 09 Jan 2023 H1 MIT No Details →
1.0.0.pre5 08 Jan 2023 H1 MIT No Details →
1.0.0.pre4 28 Dec 2022 H1 MIT No Details →
1.0.0.pre3 30 Nov 2022 H1 MIT No Details →
1.0.0.pre.2 21 Nov 2022 H1 MIT No Details →
0.23.7.pre1 14 Nov 2022 H1 M3 MIT No Details →
1.0.0.pre 03 Nov 2022 H1 MIT No Details →
0.23.6 21 Sep 2022 H1 M3 MIT No Details →
0.23.5 31 May 2022 H1 M4 MIT No Details →
0.23.4 03 Mar 2022 H1 M4 MIT No Details →
0.23.2 17 Sep 2021 H2 M4 MIT No Details →
0.23.1 03 Sep 2021 H2 M4 MIT No Details →
0.23.0 30 Aug 2021 H2 M4 MIT No Details →
0.22.0 20 Jun 2021 H2 M4 MIT No Details →
0.21.2 11 Feb 2021 H2 M4 MIT No Details →
0.21.1 21 Jan 2021 H2 M4 MIT No Details →
0.21.0 23 Jan 2020 H2 M4 MIT No Details →
0.20.2 18 Dec 2019 H2 M4 MIT No Details →
0.20.1 29 Apr 2019 H2 M4 MIT No Details →
0.20.0 09 Apr 2019 H2 M4 MIT No Details →
0.19.0 03 Apr 2019 H2 M4 MIT No Details →
0.18.2 28 Nov 2018 H2 M4 MIT No Details →
0.18.1 18 Oct 2018 H2 M4 MIT No Details →
0.18.0 17 Oct 2018 H2 M4 MIT No Details →
0.17.13 10 Sep 2018 H2 M4 MIT No Details →
0.17.12 07 Sep 2018 H2 M4 MIT No Details →
0.17.11 10 Aug 2018 H2 M4 MIT No Details →
0.17.10 08 Aug 2018 H2 M4 MIT No Details →
0.17.9 12 Mar 2018 H2 M4 MIT No Details →
0.17.8 21 Feb 2018 H2 M4 MIT No Details →
0.17.7.1 10 Dec 2017 H2 M4 MIT No Details →
0.17.7 05 Dec 2017 H2 M4 MIT No Details →
0.17.6 16 Nov 2017 H2 M4 MIT No Details →
0.17.5 19 Oct 2017 H2 M4 MIT No Details →
0.17.4 03 Oct 2017 H2 M4 MIT No Details →
0.17.2 08 Sep 2017 H2 M4 MIT No Details →
0.17.1 08 Sep 2017 H2 M4 MIT No Details →
0.17.0 25 Aug 2017 H2 M4 MIT No Details →
0.16.8 17 Jul 2017 H2 M4 MIT No Details →
0.16.7 13 Jul 2017 H2 M4 MIT No Details →
0.16.6 11 Jul 2017 H2 M4 MIT No Details →
0.16.5 30 Jun 2017 H2 M4 MIT No Details →
0.16.4 27 Jun 2017 H2 M4 MIT No Details →
0.16.1 21 Jun 2017 H2 M4 MIT No Details →
0.16.2 21 Jun 2017 H2 M4 MIT No Details →
0.16.3 21 Jun 2017 H2 M4 MIT No Details →
0.16.0 08 May 2017 H2 M4 MIT No Details →
0.15.0 22 Apr 2017 H2 M4 MIT No Details →
0.14.15 03 Apr 2017 H2 M4 MIT No Details →
0.14.14 27 Mar 2017 H2 M4 MIT No Details →
0.14.13 27 Mar 2017 H2 M4 MIT No Details →
0.14.12 22 Mar 2017 H2 M4 MIT No Details →
0.14.11 22 Mar 2017 H2 M4 — No Details →
0.14.9 20 Mar 2017 H2 M4 — No Details →
0.14.8 15 Mar 2017 H2 M4 — No Details →
0.14.7 13 Mar 2017 H2 M4 — No Details →
0.14.6 13 Mar 2017 H2 M4 — No Details →
0.14.5 06 Mar 2017 H2 M4 — No Details →
0.14.4 23 Feb 2017 H2 M4 — No Details →
0.14.3 06 Feb 2017 H2 M4 — No Details →
0.14.2 27 Jan 2017 H2 M4 — No Details →
0.14.1 23 Jan 2017 H2 M4 — No Details →
0.14.0 13 Dec 2016 H2 M4 — No Details →
0.13.0 27 Nov 2016 H2 M4 — No Details →
0.12.0 11 Oct 2016 H2 M4 — No Details →
0.11.0 18 Sep 2016 H2 M4 — No Details →
0.10.0 21 Jul 2016 H2 M4 — No Details →
0.9.2 07 Jun 2016 H2 M4 — No Details →
0.9.1 24 May 2016 H2 M4 — No Details →
0.9.0 18 May 2016 H2 M4 — No Details →
0.8.0 04 Apr 2016 H2 M4 — No Details →
0.7.0 20 Jan 2016 H2 M4 — No Details →

The newest 120 of 133 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 3
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for commonmarker

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Integer Overflow in cmark-gfm Table Parsing Extension Leads to Heap Memory Corruption in CommonMarker 8.8 high 0.23.4 03 Mar 2022
Unbounded resource exhaustion in cmark-gfm autolink extension may lead to denial of service in commonmarker N/A medium 0.23.6 21 Sep 2022
Denial of Service Vulnerability in Commonmarker N/A medium 0.23.7 24 Jan 2023
Vulnerability in Commonmarker RubyGem: Denial of Service due to Quadratic Complexity Bugs N/A medium 0.23.9 11 Apr 2023
Denial of Service Vulnerability in Commonmarker N/A medium 0.23.10 08 Aug 2023

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 commonmarker

Is commonmarker safe to use?

Vulert records 6 vulnerabilities for commonmarker in RubyGems: 0 critical, 2 high, 4 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is commonmarker's Vulert package health score?

Vulert scores commonmarker 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of commonmarker affected?

Yes. 2.10.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does commonmarker have?

6 vulnerabilities are recorded for commonmarker in the RubyGems ecosystem: 0 critical, 2 high, 4 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 commonmarker vulnerabilities disclosed?

0 vulnerabilities were recorded for commonmarker in the last 12 months, and the oldest entry in this database dates to 03 Mar 2022. 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 commonmarker 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 commonmarker for upcoming vulnerabilities?

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