VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

bibtex-ruby: vulnerability history, versions and safety

bibtex-ruby is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 85 releases, first recorded in Feb 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
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 bibtex-ruby vulnerabilities

Vulert verdict on bibtex-ruby 6.2.0 i

Updated on 23 Oct 2026

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

Package health score 62/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 6.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 14 Feb 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 160 i
  • OpenSSF scorecard 2/10 i
  • Last release 15 months ago i
  • Licence GPL-3.0-or-later 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 bibtex-ruby, 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
6.2.0 20 Jul 2025 none GPL-3.0-or-later — Details →
6.1.0 08 Jan 2024 none GPL-3.0-or-later — Details →
6.0.0 07 Jan 2021 none GPL-3.0 — Details →
5.1.6 02 Dec 2020 none GPL-3.0 — Details →
5.1.5 14 Oct 2020 none GPL-3.0 — Details →
5.1.4 14 Apr 2020 none GPL-3.0 — Details →
5.1.3 06 Apr 2020 none GPL-3.0 — Details →
5.1.2 27 Feb 2020 none GPL-3.0 — Details →
5.1.1 17 Jan 2020 none GPL-3.0 — Details →
5.1.0 17 Jan 2020 none GPL-3.0 — Details →
5.0.1 18 Nov 2019 C1 GPL-3.0 Yes Details →
5.0.0 12 Jun 2019 C1 GPL-3.0 Yes Details →
4.4.7 01 Jun 2018 C1 GPL-3.0 Yes Details →
4.4.6 01 Mar 2018 C1 GPL-3.0 Yes Details →
4.4.5 15 Jan 2018 C1 GPL-3.0 Yes Details →
4.4.4 02 Jul 2017 C1 GPL-3.0 Yes Details →
4.4.3 30 Oct 2016 C1 GPL-3.0 Yes Details →
4.4.2 15 Jul 2016 C1 GPL-3.0 Yes Details →
4.4.1 13 Jul 2016 C1 GPL-3.0 Yes Details →
4.4.0 14 May 2016 C1 GPL-3.0 Yes Details →
4.3.0 24 Mar 2016 C1 GPL-3.0 Yes Details →
4.2.0 02 Feb 2016 C1 GPL-3.0 Yes Details →
4.1.2 08 Jan 2016 C1 GPL-3.0 Yes Details →
4.1.1 07 Jan 2016 C1 GPL-3.0 Yes Details →
4.1.0 09 Dec 2015 C1 GPL-3.0 Yes Details →
4.0.16 27 Oct 2015 C1 GPL-3.0 Yes Details →
4.0.15 04 Oct 2015 C1 GPL-3.0 Yes Details →
4.0.14 25 Jun 2015 C1 GPL-3.0 Yes Details →
4.0.13 10 May 2015 C1 GPL-3.0 Yes Details →
4.0.12 25 Mar 2015 C1 GPL-3.0 Yes Details →
4.0.11 02 Mar 2015 C1 GPL-3.0 Yes Details →
4.0.10 23 Jan 2015 C1 GPL-3.0 Yes Details →
4.0.9 20 Jan 2015 C1 GPL-3.0 Yes Details →
4.0.8 12 Jan 2015 C1 GPL-3.0 Yes Details →
4.0.7 12 Jan 2015 C1 GPL-3.0 Yes Details →
4.0.6 12 Jan 2015 C1 GPL-3.0 Yes Details →
4.0.5 28 Nov 2014 C1 GPL-3.0 Yes Details →
4.0.4 10 Oct 2014 C1 GPL-3.0 Yes Details →
4.0.3 23 Jul 2014 C1 GPL-3.0 Yes Details →
4.0.2 10 Jul 2014 C1 GPL-3.0 Yes Details →
4.0.1 10 Jul 2014 C1 GPL-3.0 Yes Details →
4.0.0 08 Jul 2014 C1 GPL-3.0 Yes Details →
3.1.6 17 Jun 2014 C1 GPL-3.0 Yes Details →
3.1.5 25 Mar 2014 C1 GPL-3.0 Yes Details →
3.1.4 15 Mar 2014 C1 GPL-3.0 Yes Details →
3.1.3 10 Feb 2014 C1 GPL-3.0 Yes Details →
3.1.2 29 Jan 2014 C1 GPL-3.0 Yes Details →
3.1.1 20 Jan 2014 C1 GPL-3.0 Yes Details →
3.1.0 20 Jan 2014 C1 GPL-3.0 Yes Details →
3.0.1 30 Dec 2013 C1 GPL-3.0 Yes Details →
3.0.0 11 Nov 2013 C1 GPL-3.0 Yes Details →
2.3.4 22 Aug 2013 C1 GPL-3.0 Yes Details →
2.3.3 29 Jul 2013 C1 GPL-3.0 Yes Details →
2.3.2 08 Jun 2013 C1 GPL-3.0 Yes Details →
2.3.1 07 Apr 2013 C1 GPL-3.0 Yes Details →
2.3.0 06 Apr 2013 C1 GPL-3.0 Yes Details →
2.2.2 15 Jan 2013 C1 GPL-3.0 Yes Details →
2.2.1 13 Jan 2013 C1 GPL-3.0 Yes Details →
2.2.0 02 Dec 2012 C1 GPL-3.0 Yes Details →
2.1.2 02 Nov 2012 C1 — Yes Details →
2.1.1 14 Sep 2012 C1 — Yes Details →
2.1.0 31 Aug 2012 C1 — Yes Details →
2.0.12 28 Jun 2012 C1 — Yes Details →
2.0.11 23 May 2012 C1 — Yes Details →
2.0.10 15 May 2012 C1 — Yes Details →
2.0.9 15 May 2012 C1 — Yes Details →
2.0.8 11 May 2012 C1 — Yes Details →
2.0.7 30 Apr 2012 C1 — Yes Details →
2.0.6 30 Apr 2012 C1 — Yes Details →
2.0.5 19 Apr 2012 C1 — Yes Details →
2.0.4 20 Dec 2011 C1 — Yes Details →
2.0.3 13 Dec 2011 C1 — Yes Details →
2.0.2 25 Nov 2011 C1 — Yes Details →
2.0.1 20 Oct 2011 C1 — Yes Details →
2.0.0 25 Sep 2011 C1 — Yes Details →
2.0.0pre1 25 Sep 2011 C1 — Yes Details →
1.3.12 06 Sep 2011 C1 — Yes Details →
1.3.11 05 Aug 2011 C1 — Yes Details →
1.3.10 16 Jul 2011 C1 — Yes Details →
1.3.9 05 Jul 2011 C1 — Yes Details →
1.3.8 05 Jul 2011 C1 — Yes Details →
1.3.7 30 Jun 2011 C1 — Yes Details →
1.3.6 11 Jun 2011 C1 — Yes Details →
1.3.5 07 Jun 2011 C1 — Yes Details →
1.3.4 07 Jun 2011 C1 — Yes Details →
1.3.3 06 Jun 2011 C1 — Yes Details →
1.3.2 21 May 2011 C1 — Yes Details →
1.3.1 14 May 2011 C1 — Yes Details →
1.3.0 12 May 2011 C1 — Yes Details →
1.2.1 06 Apr 2011 C1 — Yes Details →
1.2.0 12 Feb 2011 C1 — Yes Details →
1.1.2 27 Jan 2011 C1 — Yes Details →
1.1.1 25 Jan 2011 C1 — Yes Details →
1.1.0 24 Jan 2011 C1 — Yes Details →
1.0.0 18 Jan 2011 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for bibtex-ruby

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-10780: OS command injection in BibTeX-Ruby 9.8 critical 5.1.0 14 Feb 2020

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 bibtex-ruby

Is bibtex-ruby safe to use?

Vulert records 1 vulnerabilities for bibtex-ruby in RubyGems: 1 critical, 0 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 bibtex-ruby's Vulert package health score?

Vulert scores bibtex-ruby 62/100, which reads as usable, but worth attention. 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 bibtex-ruby affected?

No. 6.2.0, 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 bibtex-ruby should I use?

6.2.0 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 bibtex-ruby have?

1 vulnerability is recorded for bibtex-ruby in the RubyGems ecosystem: 1 critical, 0 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 bibtex-ruby vulnerabilities disclosed?

0 vulnerabilities were recorded for bibtex-ruby in the last 12 months, and the oldest entry in this database dates to 14 Feb 2020. 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 bibtex-ruby 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 bibtex-ruby for upcoming vulnerabilities?

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