Is http 0.6 vulnerable?

RubyGems · 5 releases from 0.6.0 to 0.6.4 · latest http is 6.0.4 · checked 18 Nov 2026

No known advisories in the last release

http 0.6.4, the last 0.6 release, has no known advisories. 1 advisory affects earlier 0.6.x releases, so update to 0.6.4.

Update within 0.6:bundle update --conservative http # Gemfile: '>= 0.6.4'

Is your project on an affected http?

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

  • MediumCVE-2015-1828GHSA-6wpv-cj6x-v3jw13 Mar 2018

    http vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

    Affected
    >=0.7.0 <0.7.3 · <0.6.4
    Fixed in
    0.6.4, 0.7.3

Every http 0.6.x release

Affected: 0.6.0 to 0.6.3. 0.6.4 is not affected. Latest http: 6.0.4.

VersionKnown advisories
http 0.6.4None
http 0.6.3CVE-2015-1828
http 0.6.2CVE-2015-1828
http 0.6.1CVE-2015-1828
http 0.6.0CVE-2015-1828

Which of your client projects are still on http 0.6?

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

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