Is redcarpet 3.3 vulnerable?
RubyGems · 5 releases from 3.3.0 to 3.3.4 · latest redcarpet is 3.6.1 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. redcarpet 3.3.4, the last 3.3 release, is affected by 1 known security advisory (1 medium), including CVE-2020-26298. 1 more affects earlier 3.3.x releases. Upgrade to 3.5.1 or later to fix all of them.
bundle update --conservative redcarpet # Gemfile: '>= 3.5.1'Is your project on an affected redcarpet?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting redcarpet 3.3.4
Injection/XSS in Redcarpet
- Affected
- <3.5.1
- Fixed in
- 3.5.1
Fixed within 3.3.x, affecting earlier releases
redcarpet Buffer Overflow vulnerability
- Affected
- >=3.3.0 <3.3.2
- Fixed in
- 3.3.2
Every redcarpet 3.3.x release
Affected: 3.3.0 to 3.3.4. Latest redcarpet: 3.6.1.
| Version | Known advisories |
|---|---|
| redcarpet 3.3.4 | CVE-2020-26298 |
| redcarpet 3.3.3 | CVE-2020-26298 |
| redcarpet 3.3.2 | CVE-2020-26298 |
| redcarpet 3.3.1 | CVE-2020-26298, CVE-2015-5147 |
| redcarpet 3.3.0 | CVE-2020-26298, CVE-2015-5147 |
Which of your client projects are still on redcarpet 3.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact redcarpet version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other redcarpet versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.