Vulnerability Database · Go · Package report

github.com/dragonflyoss/dragonfly: vulnerability history, versions and safety

github.com/dragonflyoss/dragonfly is a package in the Go ecosystem. Vulert records 11 vulnerabilities for it across 10 releases, first recorded in Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H3 M7 L1
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.

Vulert verdict on github.com/dragonflyoss/dragonfly v0.4.1 i

Updated on 23 Oct 2026

Action needed: v0.4.1 has 11 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 77/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Active

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.4.1 — affected i
  • Vulnerabilities on record 11 over 1 year · 0 in the last year i
  • Latest disclosure 17 Sep 2025 i
  • Highest CVSS 7.7 i
  • With no published fix 0 i
  • Stars 3,353 i
  • OpenSSF scorecard 9/10 i
  • Last release 87 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/dragonflyoss/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
v0.4.1 09 Jul 2019 H3 M7 L1 Apache-2.0 Yes Details →
v0.4.0 20 Jun 2019 H3 M7 L1 Apache-2.0 Yes Details →
v0.3.1 06 Jun 2019 H3 M7 L1 Apache-2.0 Yes Details →
v0.3.1-0.20190319020647-961b5000be01 19 Mar 2019 H3 M7 L1 Apache-2.0 Yes Details →
v0.3.0 04 Mar 2019 H3 M7 L1 Apache-2.0 Yes Details →
v0.2.1 13 Feb 2019 H3 M7 L1 Apache-2.0 Yes Details →
v0.2.0 03 Aug 2018 H3 M7 L1 Apache-2.0 Yes Details →
v0.1.1 27 Jun 2018 H3 M7 L1 Apache-2.0 Yes Details →
v0.1.0 30 May 2018 H3 M7 L1 Apache-2.0 Yes Details →
v0.0.1 02 May 2018 H3 M7 L1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 11

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 11 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 github.com/dragonflyoss/dragonfly

Is github.com/dragonflyoss/dragonfly safe to use?

Vulert records 11 vulnerabilities for github.com/dragonflyoss/dragonfly in Go: 0 critical, 3 high, 7 medium and 1 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 github.com/dragonflyoss/dragonfly's Vulert package health score?

Vulert scores github.com/dragonflyoss/dragonfly 77/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 github.com/dragonflyoss/dragonfly affected?

Yes. v0.4.1, the version you would install today, has 11 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/dragonflyoss/dragonfly should I use?

v0.4.1 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 github.com/dragonflyoss/dragonfly have?

11 vulnerabilities are recorded for github.com/dragonflyoss/dragonfly in the Go ecosystem: 0 critical, 3 high, 7 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/dragonflyoss/dragonfly vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/dragonflyoss/dragonfly in the last 12 months, and the oldest entry in this database dates to 17 Sep 2025. 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 github.com/dragonflyoss/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 github.com/dragonflyoss/dragonfly for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/dragonflyoss/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.