Is jwt 1.4 vulnerable?

RubyGems · 2 releases from 1.4.0 to 1.4.1 · latest jwt is 3.3.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. jwt 1.4.1, the last 1.4 release, is affected by 1 known security advisory (1 high), including CVE-2026-45363. Upgrade to 2.10.3 or later to fix all of them.

Upgrade with:bundle update --conservative jwt # Gemfile: '>= 2.10.3'

Is your project on an affected jwt?

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

Advisories affecting jwt 1.4.1

  • HighCVE-2026-45363GHSA-c32j-vqhx-rx3x18 May 2026

    ruby-jwt: Empty-key HMAC bypass; cross-language sibling of CVE-2026-44351

    Affected
    >=3.0.0 <3.2.0 · <2.10.3
    Fixed in
    2.10.3, 3.2.0

Every jwt 1.4.x release

Affected: 1.4.0 to 1.4.1. Latest jwt: 3.3.0.

VersionKnown advisories
jwt 1.4.1CVE-2026-45363
jwt 1.4.0CVE-2026-45363

Which of your client projects are still on jwt 1.4?

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

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