Is time 0.1 vulnerable?
RubyGems · 2 releases from 0.1.0 to 0.1.1 · latest time is 0.5.0 · checked 18 Nov 2026
No known advisories in the last release
time 0.1.1, the last 0.1 release, has no known advisories. 1 advisory affects earlier 0.1.x releases, so update to 0.1.1.
bundle update --conservative time # Gemfile: '>= 0.1.1'Is your project on an affected time?
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.1.x, affecting earlier releases
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.1.x release
Affected: 0.1.0. 0.1.1 is not affected. Latest time: 0.5.0.
| Version | Known advisories |
|---|---|
| time 0.1.1 | None |
| time 0.1.0 | CVE-2023-28756 |
Which of your client projects are still on time 0.1?
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.