Is better_errors 0.3 vulnerable?

RubyGems · 2 releases from 0.3.0 to 0.3.2 · latest better_errors is 2.10.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. better_errors 0.3.2, the last 0.3 release, is affected by 1 known security advisory (1 medium), including CVE-2021-39197. Upgrade to 2.8.0 or later to fix all of them.

Upgrade with:bundle update --conservative better_errors # Gemfile: '>= 2.8.0'

Is your project on an affected better_errors?

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 better_errors 0.3.2

  • MediumCVE-2021-39197GHSA-w3j4-76qw-wwjm7 Sept 2021

    Older releases of better_errors open to Cross-Site Request Forgery attack

    Affected
    <2.8.0
    Fixed in
    2.8.0

Every better_errors 0.3.x release

Affected: 0.3.0 to 0.3.2. Latest better_errors: 2.10.1.

VersionKnown advisories
better_errors 0.3.2CVE-2021-39197
better_errors 0.3.0CVE-2021-39197

Which of your client projects are still on better_errors 0.3?

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

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