Is geocoder 1.6 vulnerable?

RubyGems · 8 releases from 1.6.0 to 1.6.7 · latest geocoder is 1.8.6 · checked 18 Nov 2026

No known advisories in the last release

geocoder 1.6.7, the last 1.6 release, has no known advisories. 1 advisory affects earlier 1.6.x releases, so update to 1.6.7.

Update within 1.6:bundle update --conservative geocoder # Gemfile: '>= 1.6.7'

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

Fixed within 1.6.x, affecting earlier releases

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

    SQL Injection in Geocoder

    Affected
    <1.6.1
    Fixed in
    1.6.1

Every geocoder 1.6.x release

Affected: 1.6.0. 1.6.1 and later are not affected. Latest geocoder: 1.8.6.

VersionKnown advisories
geocoder 1.6.7None
geocoder 1.6.6None
geocoder 1.6.5None
geocoder 1.6.4None
geocoder 1.6.3None
geocoder 1.6.2None
geocoder 1.6.1None
geocoder 1.6.0CVE-2020-7981

Which of your client projects are still on geocoder 1.6?

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.