Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
CRITICAL severity

Remote code execution in KramdownGHSA-52p9-v744-mwjj

CRITICALFix: gettalong/kramdown#708

GHSA-52p9-v744-mwjj is a critical-severity (CVSS 9.8) vulnerability in kramdown. 1 public exploit reference exists, so weaponization risk is real. A fix is available for kramdown — see the affected versions and patch details below.

Also known asCVE-2021-28834
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.7%probability of exploitation in next 30 days
Lower Risk-0.11%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
2.09%2.49%2.90%3.30%2.6%2.7%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-52p9-v744-mwjj by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
💎kramdown

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Kramdown before 2.3.1 does not restrict Rouge formatters to the Rouge::Formatters namespace, and thus arbitrary classes can be instantiated.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemskramdown≥ 1.16.0&&< 2.3.12.3.1bundle update kramdown --conservative

Affected Products

3 products · 5 configurations
OS
debian linuxdebian
1 version
10.0
OS
fedorafedoraproject
3 versions
323334
Application
kramdownkramdown_project
< 2.3.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kramdown, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update kramdown to 2.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-52p9-v744-mwjj is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat supported products are not affected by this flaw because they do not ship rubygem-kramdown.

Workaround published by Red Hat
Developers using rubygem-kramdown: Do not pass user or external input into custom Rouge formatter selection logic. All other users/system administrators: There is no known mitigation at this time.
Source: Red Hat security advisory for GHSA-52p9-v744-mwjj (CC BY 4.0)
UbuntuCRITICAL

Frequently Asked Questions

Kramdown before 2.3.1 does not restrict Rouge formatters to the Rouge::Formatters namespace, and thus arbitrary classes can be instantiated.
O3 Security · Impact-Aware SCA

Is GHSA-52p9-v744-mwjj in your dependencies?

Find it across RubyGems, including transitive dependencies.

Remote code execution in Kramdown (Critical 9.8)