VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

datagrid: vulnerability history, versions and safety

datagrid is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 86 releases, first recorded in Jul 2019. 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
1 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.

See all datagrid vulnerabilities

Vulert verdict on datagrid 2.0.9 i

Updated on 23 Oct 2026

Careful: 2.0.9 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.0.9 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 31 Jul 2019 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 1,113 i
  • OpenSSF scorecard 2/10 i
  • Last release 10 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 datagrid, 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.0.9 18 Dec 2025 C1 MIT No Details →
2.0.8 30 Nov 2025 C1 MIT No Details →
2.0.7 18 Nov 2025 C1 MIT No Details →
2.0.5 17 Oct 2025 C1 MIT No Details →
2.0.3 07 Jul 2025 C1 MIT No Details →
2.0.1 27 Jan 2025 C1 MIT No Details →
2.0.0 20 Nov 2024 C1 MIT No Details →
2.0.0.pre.alpha 19 Nov 2024 C1 MIT No Details →
1.8.2 22 Sep 2024 C1 MIT No Details →
1.8.1 05 Jan 2024 C1 MIT No Details →
1.8.0 12 Dec 2023 C1 MIT No Details →
1.7.0 22 Jan 2023 C1 MIT No Details →
1.6.3 04 Aug 2021 C1 MIT No Details →
1.6.2 02 Aug 2021 C1 MIT No Details →
1.6.1 07 Sep 2020 C1 MIT No Details →
1.6.0 31 Mar 2020 C1 MIT No Details →
1.5.9 10 May 2019 C1 MIT No Details →
1.5.8 12 Dec 2017 C1 MIT No Details →
1.5.7 30 Oct 2017 C1 MIT No Details →
1.5.6 30 Oct 2017 C1 MIT No Details →
1.5.5 03 Oct 2017 C1 MIT No Details →
1.5.4 16 Jun 2017 C1 MIT No Details →
1.5.3 06 Mar 2017 C1 MIT No Details →
1.5.2 28 Feb 2017 C1 MIT No Details →
1.5.1 25 Oct 2016 C1 MIT No Details →
1.5.0 13 Oct 2016 C1 MIT No Details →
1.4.4 22 Jul 2016 C1 MIT No Details →
1.4.3 31 Mar 2016 C1 MIT No Details →
1.4.2 08 Mar 2016 C1 MIT No Details →
1.4.1 10 Feb 2016 C1 MIT No Details →
1.4.0 05 Nov 2015 C1 MIT No Details →
1.3.9 11 May 2015 C1 MIT No Details →
1.3.7 25 Mar 2015 C1 MIT No Details →
1.3.6 05 Feb 2015 C1 MIT No Details →
1.3.5 21 Jan 2015 C1 MIT No Details →
1.3.4 08 Jan 2015 C1 MIT No Details →
1.3.3 12 Nov 2014 C1 MIT No Details →
1.3.2 27 Oct 2014 C1 MIT No Details →
1.3.1 21 Aug 2014 C1 MIT No Details →
1.3.0 23 Jul 2014 C1 MIT No Details →
1.2.3 01 Jul 2014 C1 MIT No Details →
1.2.2 24 May 2014 C1 MIT No Details →
1.2.1 19 May 2014 C1 MIT No Details →
1.2.0 10 May 2014 C1 MIT No Details →
1.1.2 17 Mar 2014 C1 MIT No Details →
1.1.1 08 Mar 2014 C1 MIT No Details →
1.1.0 07 Mar 2014 C1 MIT No Details →
1.0.5 15 Jan 2014 C1 MIT No Details →
1.0.4 15 Jan 2014 C1 MIT No Details →
1.0.3 27 Nov 2013 C1 MIT No Details →
1.0.2 25 Nov 2013 C1 MIT No Details →
1.0.1 14 Oct 2013 C1 MIT No Details →
1.0.0 19 Sep 2013 C1 MIT No Details →
0.9.3 26 Aug 2013 C1 MIT No Details →
0.9.2 23 Aug 2013 C1 MIT No Details →
0.9.0 06 Jun 2013 C1 MIT No Details →
0.8.4 22 May 2013 C1 MIT No Details →
0.8.3 20 May 2013 C1 MIT No Details →
0.8.2 15 May 2013 C1 MIT No Details →
0.8.1 28 Apr 2013 C1 MIT No Details →
0.8.0 07 Apr 2013 C1 MIT No Details →
0.7.1 15 Jan 2013 C1 MIT No Details →
0.7.0 15 Dec 2012 C1 MIT No Details →
0.6.4 17 Sep 2012 C1 — No Details →
0.6.3 28 Aug 2012 C1 — No Details →
0.6.2 22 Jun 2012 C1 — No Details →
0.6.0 24 May 2012 C1 — No Details →
0.5.4 11 Apr 2012 C1 — No Details →
0.5.3 13 Feb 2012 C1 — No Details →
0.5.2 26 Jan 2012 C1 — No Details →
0.5.1 26 Jan 2012 C1 — No Details →
0.5.0 03 Jan 2012 C1 — No Details →
0.4.1 06 Dec 2011 C1 — No Details →
0.4.0 03 Nov 2011 C1 — No Details →
0.3.6 22 Aug 2011 C1 — No Details →
0.3.5 15 Aug 2011 C1 — No Details →
0.3.4 10 Aug 2011 C1 — No Details →
0.3.3 07 Jul 2011 C1 — No Details →
0.3.2 07 Jul 2011 C1 — No Details →
0.3.1 07 Jul 2011 C1 — No Details →
0.3.0 01 Jul 2011 C1 — No Details →
0.2.0 22 Jun 2011 C1 — No Details →
0.1.2 22 Jun 2011 C1 — No Details →
0.1.1 22 Jun 2011 C1 — No Details →
0.1.0 21 Jun 2011 C1 — No Details →
0.0.3 10 Jun 2011 C1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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 datagrid

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-14281: Code Injection in datagrid 9.8 critical No fix published 31 Jul 2019

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 datagrid

Is datagrid safe to use?

Vulert records 1 vulnerabilities for datagrid in RubyGems: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is datagrid's Vulert package health score?

Vulert scores datagrid 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of datagrid affected?

Yes. 2.0.9, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of datagrid should I use?

2.0.9 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 datagrid have?

1 vulnerability is recorded for datagrid 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 datagrid vulnerabilities disclosed?

0 vulnerabilities were recorded for datagrid in the last 12 months, and the oldest entry in this database dates to 31 Jul 2019. 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 datagrid 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 datagrid for upcoming vulnerabilities?

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