Is date 3.1 vulnerable?

RubyGems · 4 releases from 3.1.0 to 3.1.3 · latest date is 3.6.0 · checked 18 Nov 2026

No known advisories in the last release

date 3.1.3, the last 3.1 release, has no known advisories. 1 advisory affects earlier 3.1.x releases, so update to 3.1.3.

Update within 3.1:bundle update --conservative date # Gemfile: '>= 3.1.3'

Is your project on an affected date?

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 3.1.x, affecting earlier releases

  • HighCVE-2021-41817GHSA-qg54-694p-wgpp16 Nov 2021

    Regular expression denial of service vulnerability (ReDoS) in date

    Affected
    >=3.2.0 <3.2.1 · >=3.1.0 <3.1.2 · >=3.0.0 <3.0.2 · <2.0.1
    Fixed in
    2.0.1, 3.0.2, 3.1.2, 3.2.1

Every date 3.1.x release

Affected: 3.1.0 to 3.1.1. 3.1.2 and later are not affected. Latest date: 3.6.0.

VersionKnown advisories
date 3.1.3None
date 3.1.2None
date 3.1.1CVE-2021-41817
date 3.1.0CVE-2021-41817

Which of your client projects are still on date 3.1?

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

Other date 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.