Vulnerability Database · Debian · Package report

glusterfs: vulnerability history, versions and safety

glusterfs is a package in the Debian ecosystem. Vulert records 52 vulnerabilities for it across 34 releases, from Nov 2012 to Feb 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
52 vulnerabilities recorded U52
i
2 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.

Vulert verdict on glusterfs i

Updated on 23 Oct 2026

Careful: 2 of the 52 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 52 vulnerabilities on record across 10 years, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 52 over 10 years · 0 in the last year i
  • Latest disclosure 21 Feb 2023 i
  • Highest CVSS 8.8 i
  • With no published fix 2 i

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 holds for glusterfs, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 34 of 34 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2012 2
  • 2013 2
  • 2015 2
  • 2017 2
  • 2018 42
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 52 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 glusterfs

Is glusterfs safe to use?

Vulert records 52 vulnerabilities for glusterfs in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 52 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does glusterfs have?

52 vulnerabilities are recorded for glusterfs in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 52 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new glusterfs vulnerabilities disclosed?

0 vulnerabilities were recorded for glusterfs in the last 12 months, and the oldest entry in this database dates to 18 Nov 2012. 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 glusterfs 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 glusterfs for upcoming vulnerabilities?

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