Is time 0.2 vulnerable?

RubyGems · 3 releases from 0.2.0 to 0.2.2 · latest time is 0.5.0 · checked 18 Nov 2026

No known advisories in the last release

time 0.2.2, the last 0.2 release, has no known advisories. 1 advisory affects earlier 0.2.x releases, so update to 0.2.2.

Update within 0.2:bundle update --conservative time # Gemfile: '>= 0.2.2'

Is your project on an affected time?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 0.2.x, affecting earlier releases

  • HighCVE-2023-28756GHSA-fg7x-g82r-94qc31 Mar 2023

    Ruby Time component ReDoS issue

    Affected
    >=0.2.0 <0.2.2 · <0.1.1
    Fixed in
    0.1.1, 0.2.2

Every time 0.2.x release

Affected: 0.2.0 to 0.2.1. 0.2.2 is not affected. Latest time: 0.5.0.

VersionKnown advisories
time 0.2.2None
time 0.2.1CVE-2023-28756
time 0.2.0CVE-2023-28756

Which of your client projects are still on time 0.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact time version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other time versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.