VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

dragonfly: vulnerability history, versions and safety

dragonfly is a package in the RubyGems ecosystem. Vulert records 4 vulnerabilities for it across 80 releases, from Oct 2017 to Jun 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 dragonfly vulnerabilities

Vulert verdict on dragonfly 1.4.2 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 1.4.2 — unaffected i
  • Vulnerabilities on record 4 over 4 years · 0 in the last year i
  • Latest disclosure 03 Jun 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 2,106 i
  • OpenSSF scorecard 1/10 i
  • Last release 3 months ago 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 dragonfly, 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
1.4.2 21 Jul 2026 none MIT — Details →
1.4.1 03 Jan 2025 none MIT — Details →
1.4.0 19 May 2021 none MIT — Details →
1.3.0 09 Jan 2021 C2 MIT Yes Details →
1.2.1 24 Jul 2020 C2 MIT Yes Details →
1.2.0 13 Nov 2018 C2 MIT Yes Details →
1.1.5 23 Mar 2018 C2 MIT Yes Details →
1.1.4 31 Dec 2017 C2 MIT Yes Details →
1.1.3 02 Jun 2017 C2 MIT Yes Details →
1.1.2 06 May 2017 C2 MIT Yes Details →
1.1.1 26 Oct 2016 C2 MIT Yes Details →
1.1.0 24 Oct 2016 C2 MIT Yes Details →
1.0.12 16 Sep 2015 C2 MIT Yes Details →
1.0.11 04 Sep 2015 C2 MIT Yes Details →
1.0.10 14 May 2015 C2 MIT Yes Details →
1.0.9 29 Apr 2015 C2 MIT Yes Details →
1.0.8 23 Apr 2015 C2 MIT Yes Details →
1.0.7 26 Aug 2014 C2 MIT Yes Details →
1.0.6 22 Aug 2014 C2 MIT Yes Details →
1.0.5 15 May 2014 C2 MIT Yes Details →
1.0.4 11 Apr 2014 C2 MIT Yes Details →
1.0.3 28 Jan 2014 C2 MIT Yes Details →
1.0.2 20 Dec 2013 C2 MIT Yes Details →
1.0.1 28 Nov 2013 C2 MIT Yes Details →
1.0 24 Nov 2013 C2 MIT Yes Details →
0.9.15 04 May 2013 C2 H1 MIT Yes Details →
0.8.6 26 Mar 2013 C2 H1 — Yes Details →
0.9.14 13 Feb 2013 C2 H1 MIT Yes Details →
0.9.13 30 Jan 2013 C2 H1 MIT Yes Details →
0.9.12 08 Apr 2012 C2 H1 — Yes Details →
0.9.11 12 Mar 2012 C2 H1 — Yes Details →
0.9.10 11 Jan 2012 C2 H1 — Yes Details →
0.9.9 30 Dec 2011 C2 H1 — Yes Details →
0.9.8 08 Sep 2011 C2 H1 — Yes Details →
0.9.5 02 Aug 2011 C2 H1 — Yes Details →
0.9.4 10 Jun 2011 C2 H1 — Yes Details →
0.9.3 03 Jun 2011 C2 H1 — Yes Details →
0.9.2 19 May 2011 C2 H1 — Yes Details →
0.8.5 11 May 2011 C2 H2 — Yes Details →
0.9.1 11 May 2011 C2 H1 — Yes Details →
0.9.0 27 Apr 2011 C2 H1 — Yes Details →
0.8.4 27 Apr 2011 C2 H2 — Yes Details →
0.8.2 11 Jan 2011 C2 H2 — Yes Details →
0.8.1 22 Nov 2010 C2 H2 — Yes Details →
0.8.0 21 Nov 2010 C2 H2 — Yes Details →
0.7.7 30 Oct 2010 C2 H2 — Yes Details →
0.7.6 12 Sep 2010 C2 H2 — Yes Details →
0.7.5 01 Sep 2010 C2 H2 — Yes Details →
0.7.4 28 Aug 2010 C2 H2 — Yes Details →
0.7.3 27 Aug 2010 C2 H2 — Yes Details →
0.7.2 27 Aug 2010 C2 H2 — Yes Details →
0.7.1 26 Aug 2010 C2 H2 — Yes Details →
0.7.0 24 Aug 2010 C2 H2 — Yes Details →
0.6.2 24 Jun 2010 C2 H1 — Yes Details →
0.6.1 16 May 2010 C2 H1 — Yes Details →
0.6.0 11 May 2010 C2 H1 — Yes Details →
0.5.7 18 Apr 2010 C2 H1 — Yes Details →
0.5.6 13 Apr 2010 C2 H1 — Yes Details →
0.5.5 13 Apr 2010 C2 H1 — Yes Details →
0.5.4 12 Apr 2010 C2 H1 — Yes Details →
0.5.3 27 Mar 2010 C2 H1 — Yes Details →
0.5.2 04 Mar 2010 C2 H1 — Yes Details →
0.5.1 20 Feb 2010 C2 H1 — Yes Details →
0.5.0 20 Feb 2010 C2 H1 — Yes Details →
0.4.4 16 Feb 2010 C2 H1 — Yes Details →
0.4.3 24 Jan 2010 C2 H1 — Yes Details →
0.4.2 10 Jan 2010 C2 H1 — Yes Details →
0.4.1 07 Jan 2010 C2 H1 — Yes Details →
0.4.0 04 Jan 2010 C2 H1 — Yes Details →
0.3.8 02 Jan 2010 C2 H1 — Yes Details →
0.3.7 02 Jan 2010 C2 H1 — Yes Details →
0.3.6 19 Dec 2009 C2 H1 — Yes Details →
0.3.5 17 Dec 2009 C2 H1 — Yes Details →
0.3.4 16 Dec 2009 C2 H1 — Yes Details →
0.3.3 16 Dec 2009 C2 H1 — Yes Details →
0.3.2 15 Dec 2009 C2 H1 — Yes Details →
0.3.0 15 Dec 2009 C2 H1 — Yes Details →
0.2.1 11 Dec 2009 C2 H1 — Yes Details →
0.1.6 18 Nov 2009 C2 H1 — Yes Details →
0.1.5 18 Nov 2009 C2 H1 — Yes Details →
0.1.4 18 Nov 2009 C2 H1 — Yes Details →
0.1.1 14 Nov 2009 C2 H1 — Yes Details →
0.1.0 10 Nov 2009 C2 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 2
  • 2021 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for dragonfly

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-33564: Remote Code Execution in Dragonfly 9.8 critical 1.4.0 02 Jun 2021
CVE-2021-33473: Arbitrary file write in dragonfly 9.1 critical 1.4.0 03 Jun 2022
CVE-2013-1756: Dragonfly Code Injection vulnerability N/A high 0.8.6 24 Oct 2017
CVE-2013-5671: Code injection in dragonfly gem N/A high 1.0.0 24 Oct 2017

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 dragonfly

Is dragonfly safe to use?

Vulert records 4 vulnerabilities for dragonfly in RubyGems: 2 critical, 2 high, 0 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.

What is dragonfly's Vulert package health score?

Vulert scores dragonfly 74/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 dragonfly affected?

No. 1.4.2, 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 dragonfly should I use?

1.4.2 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 dragonfly have?

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

0 vulnerabilities were recorded for dragonfly in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 dragonfly 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 dragonfly for upcoming vulnerabilities?

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