VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

ox: vulnerability history, versions and safety

ox is a package in the RubyGems ecosystem. Vulert records 2 vulnerabilities for it across 73 releases, from Nov 2017 to Mar 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
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 ox vulnerabilities

Vulert verdict on ox 2.14.29 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.14.29 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Mar 2018 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 912 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 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 ox, 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
2.14.29 08 Aug 2026 none MIT — Details →
2.14.28 28 Jun 2026 none MIT — Details →
2.14.27 18 Jun 2026 none MIT — Details →
2.14.26 09 May 2026 none MIT — Details →
2.14.25 23 Apr 2026 none MIT — Details →
2.14.24 20 Apr 2026 none MIT — Details →
2.14.23 28 May 2025 none MIT — Details →
2.14.22 11 Feb 2025 none MIT — Details →
2.14.21 25 Jan 2025 none MIT — Details →
2.14.20 12 Jan 2025 none MIT — Details →
2.14.19 25 Dec 2024 none MIT — Details →
2.14.18 21 Mar 2024 none MIT — Details →
2.14.17 14 Jul 2023 none MIT — Details →
2.14.16 12 Apr 2023 none MIT — Details →
2.14.15 10 Apr 2023 none MIT — Details →
2.14.14 27 Jan 2023 none MIT — Details →
2.14.13 16 Jan 2023 none MIT — Details →
2.14.12 27 Dec 2022 none MIT — Details →
2.14.11 31 Mar 2022 none MIT — Details →
2.14.10 11 Mar 2022 none MIT — Details →
2.14.9 11 Feb 2022 none MIT — Details →
2.14.8 09 Feb 2022 none MIT — Details →
2.14.7 04 Feb 2022 none MIT — Details →
2.14.6 03 Nov 2021 none MIT — Details →
2.14.5 05 Jun 2021 none MIT — Details →
2.14.4 19 Mar 2021 none MIT — Details →
2.14.3 12 Mar 2021 none MIT — Details →
2.14.2 07 Mar 2021 none MIT — Details →
2.14.1 11 Jan 2021 none MIT — Details →
2.14.0 16 Dec 2020 none MIT — Details →
2.13.4 12 Sep 2020 none MIT — Details →
2.13.3 03 Sep 2020 none MIT — Details →
2.13.2 06 Feb 2020 none MIT — Details →
2.13.1 30 Jan 2020 none MIT — Details →
2.12.1 05 Jan 2020 none MIT — Details →
2.12.0 19 Dec 2019 none MIT — Details →
2.11.0 14 Jun 2019 none MIT — Details →
2.10.1 28 May 2019 none MIT — Details →
2.10.0 03 Sep 2018 none MIT — Details →
2.9.4 17 Jul 2018 none MIT — Details →
2.9.3 13 Jun 2018 none MIT — Details →
2.9.2 16 Apr 2018 none MIT — Details →
2.9.1 14 Apr 2018 none MIT — Details →
2.9.0 13 Mar 2018 none MIT — Details →
2.8.4 05 Mar 2018 none MIT — Details →
2.8.3 03 Mar 2018 none MIT — Details →
2.8.2 01 Nov 2017 none MIT — Details →
2.8.1 27 Oct 2017 M1 MIT Yes Details →
2.8.0 22 Sep 2017 H1 M1 MIT Yes Details →
2.7.0 19 Sep 2017 H1 M1 MIT Yes Details →
2.6.0 09 Aug 2017 H1 M1 MIT Yes Details →
2.5.0 05 May 2017 H1 M1 MIT Yes Details →
2.4.13 22 Apr 2017 H1 M1 MIT Yes Details →
2.4.12 12 Apr 2017 H1 M1 MIT Yes Details →
2.4.11 19 Mar 2017 H1 M1 MIT Yes Details →
2.4.9 25 Jan 2017 H1 M1 MIT Yes Details →
2.4.8 15 Jan 2017 H1 M1 MIT Yes Details →
2.4.7 25 Dec 2016 H1 M1 MIT Yes Details →
2.4.6 29 Nov 2016 H1 M1 MIT Yes Details →
2.4.5 11 Sep 2016 H1 M1 MIT Yes Details →
2.4.4 09 Aug 2016 H1 M1 MIT Yes Details →
2.4.3 27 Jun 2016 H1 M1 MIT Yes Details →
2.4.2 23 Jun 2016 H1 M1 MIT Yes Details →
2.4.1 30 Apr 2016 H1 M1 MIT Yes Details →
2.4.0 15 Apr 2016 H1 M1 MIT Yes Details →
2.3.0 22 Feb 2016 H1 M1 MIT Yes Details →
2.2.4 05 Feb 2016 H1 M1 MIT Yes Details →
2.2.3 01 Jan 2016 H1 M1 MIT Yes Details →
2.2.2 19 Oct 2015 H1 M1 MIT Yes Details →
2.2.1 31 Jul 2015 H1 M1 MIT Yes Details →
2.2.0 20 Apr 2015 H1 M1 MIT Yes Details →
2.1.8 11 Feb 2015 H1 M1 MIT Yes Details →
2.1.7 31 Jan 2015 H1 M1 MIT Yes Details →
2.1.6 31 Dec 2014 H1 M1 MIT Yes Details →
2.1.5 30 Dec 2014 H1 M1 MIT Yes Details →
2.1.4 06 Dec 2014 H1 M1 MIT Yes Details →
2.1.3 25 Jul 2014 H1 M1 MIT Yes Details →
2.1.2 17 Jul 2014 H1 M1 MIT Yes Details →
2.1.1 13 Feb 2014 H1 M1 MIT Yes Details →
2.1.0 02 Feb 2014 H1 M1 MIT Yes Details →
2.0.12 01 Dec 2013 H1 M1 MIT Yes Details →
2.0.11 17 Oct 2013 H1 M1 MIT Yes Details →
2.0.9 02 Sep 2013 H1 M1 — Yes Details →
2.0.8 07 Aug 2013 H1 M1 — Yes Details →
2.0.7 04 Aug 2013 H1 M1 — Yes Details →
2.0.6 24 Jul 2013 H1 M1 — Yes Details →
2.0.5 05 Jul 2013 H1 M1 — Yes Details →
2.0.4 25 Jun 2013 H1 M1 — Yes Details →
2.0.3 12 Jun 2013 H1 M1 — Yes Details →
2.0.2 08 Jun 2013 H1 M1 — Yes Details →
2.0.1 21 May 2013 H1 M1 — Yes Details →
2.0.0 17 Apr 2013 H1 M1 — Yes Details →
1.9.4 25 Mar 2013 H1 M1 — Yes Details →
1.9.3 23 Mar 2013 H1 M1 — Yes Details →
1.9.2 10 Mar 2013 H1 M1 — Yes Details →
1.9.1 28 Feb 2013 H1 M1 — Yes Details →
1.9.0 26 Feb 2013 H1 M1 — Yes Details →
1.8.9 22 Feb 2013 H1 M1 — Yes Details →
1.8.8 18 Feb 2013 H1 M1 — Yes Details →
1.8.7 09 Feb 2013 H1 M1 — Yes Details →
1.8.6 08 Feb 2013 H1 M1 — Yes Details →
1.8.5 04 Feb 2013 H1 M1 — Yes Details →
1.8.4 26 Jan 2013 H1 M1 — Yes Details →
1.8.3 24 Jan 2013 H1 M1 — Yes Details →
1.8.2 18 Jan 2013 H1 M1 — Yes Details →
1.8.1 17 Dec 2012 H1 M1 — Yes Details →
1.8.0 11 Dec 2012 H1 M1 — Yes Details →
1.7.1 07 Dec 2012 H1 M1 — Yes Details →
1.7.0 28 Nov 2012 H1 M1 — Yes Details →
1.6.9 26 Nov 2012 H1 M1 — Yes Details →
1.6.8 19 Nov 2012 H1 M1 — Yes Details →
1.6.7 15 Nov 2012 H1 M1 — Yes Details →
1.6.6 03 Nov 2012 H1 M1 — Yes Details →
1.6.5 25 Oct 2012 H1 M1 — Yes Details →
1.6.4 24 Oct 2012 H1 M1 — Yes Details →
1.6.3 23 Oct 2012 H1 M1 — Yes Details →
1.6.2 08 Oct 2012 H1 M1 — Yes Details →
1.6.1 08 Oct 2012 H1 M1 — Yes Details →
1.6.0 23 Sep 2012 H1 M1 — Yes Details →
1.5.9 07 Aug 2012 H1 M1 — Yes Details →

The newest 120 of 164 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for ox

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-15928: Ox gem crashes due to a crafted input 7.5 high 2.8.1 21 Nov 2017
CVE-2017-16229: ox Out-of-bounds Read vulnerability 5.5 medium 2.8.2 05 Mar 2018

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 ox

Is ox safe to use?

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

Vulert scores ox 79/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 ox affected?

No. 2.14.29, 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 ox should I use?

2.14.29 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 ox have?

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

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

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