Is geocoder 0.9 vulnerable?

RubyGems · 6 releases from 0.9.8 to 0.9.13 · latest geocoder is 1.8.6 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. geocoder 0.9.13, the last 0.9 release, is affected by 1 known security advisory (1 critical), including CVE-2020-7981. Upgrade to 1.6.1 or later to fix all of them.

Upgrade with:bundle update --conservative geocoder # Gemfile: '>= 1.6.1'

Is your project on an affected geocoder?

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 geocoder 0.9.13

  • CriticalCVE-2020-7981GHSA-864j-6qpp-cmrr10 Jun 2020

    SQL Injection in Geocoder

    Affected
    <1.6.1
    Fixed in
    1.6.1

Every geocoder 0.9.x release

Affected: 0.9.8 to 0.9.13. Latest geocoder: 1.8.6.

VersionKnown advisories
geocoder 0.9.13CVE-2020-7981
geocoder 0.9.12CVE-2020-7981
geocoder 0.9.11CVE-2020-7981
geocoder 0.9.10CVE-2020-7981
geocoder 0.9.9CVE-2020-7981
geocoder 0.9.8CVE-2020-7981

Which of your client projects are still on geocoder 0.9?

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

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