VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

http: vulnerability history, versions and safety

http is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 20 releases, first recorded in Mar 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all http vulnerabilities

Vulert verdict on http 6.0.4 i

Updated on 23 Oct 2026

Good news: 6.0.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on 6.0.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.0.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.0.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 Mar 2018 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Stars 3,083 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for http, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.0.4 14 Jul 2026 none MIT — Details →
6.0.3 20 Apr 2026 none MIT — Details →
6.0.2 20 Mar 2026 none MIT — Details →
6.0.1 17 Mar 2026 none MIT — Details →
6.0.0 17 Mar 2026 none MIT — Details →
5.3.1 09 Jun 2025 none MIT — Details →
5.3.0 09 Jun 2025 none MIT — Details →
5.2.0 05 Feb 2024 none MIT — Details →
5.1.1 17 Dec 2022 none MIT — Details →
5.1.0 17 Jun 2022 none MIT — Details →
5.0.4 07 Oct 2021 none MIT — Details →
5.0.3 06 Oct 2021 none MIT — Details →
5.0.2 10 Sep 2021 none MIT — Details →
5.0.1 26 Jun 2021 none MIT — Details →
5.0.0 13 May 2021 none MIT — Details →
4.4.1 29 Mar 2020 none MIT — Details →
4.4.0 25 Mar 2020 none MIT — Details →
5.0.0.pre3 26 Feb 2020 none MIT — Details →
5.0.0.pre2 23 Jan 2020 none MIT — Details →
4.3.0 09 Jan 2020 none MIT — Details →
4.2.0 22 Oct 2019 none MIT — Details →
4.1.1 12 Mar 2019 none MIT — Details →
4.1.0 11 Mar 2019 none MIT — Details →
4.0.5 15 Feb 2019 none MIT — Details →
4.0.4 12 Feb 2019 none MIT — Details →
5.0.0.pre 04 Feb 2019 none MIT — Details →
4.0.3 18 Jan 2019 none MIT — Details →
4.0.2 15 Jan 2019 none MIT — Details →
4.0.1 14 Jan 2019 none MIT — Details →
4.0.0 14 Oct 2018 none MIT — Details →
3.3.0 25 Apr 2018 none MIT — Details →
3.2.1 24 Apr 2018 none MIT — Details →
3.2.0 22 Apr 2018 none MIT — Details →
3.1.0 22 Apr 2018 none MIT — Details →
3.0.0 01 Oct 2017 none MIT — Details →
3.0.0.pre 10 Sep 2017 none MIT — Details →
2.2.2 27 Apr 2017 none MIT — Details →
2.2.1 06 Feb 2017 none MIT — Details →
2.2.0 03 Feb 2017 none MIT — Details →
2.1.0 09 Nov 2016 none MIT — Details →
2.0.3 03 Aug 2016 none MIT — Details →
2.0.2 24 Jun 2016 none MIT — Details →
2.0.1 12 May 2016 none MIT — Details →
2.0.0 23 Apr 2016 none MIT — Details →
2.0.0.pre 03 Apr 2016 none MIT — Details →
1.0.4 19 Mar 2016 none MIT — Details →
0.9.9 16 Mar 2016 none MIT — Details →
1.0.3 16 Mar 2016 none MIT — Details →
1.0.2 15 Jan 2016 none MIT — Details →
1.0.1 27 Dec 2015 none MIT — Details →
1.0.0 25 Dec 2015 none MIT — Details →
1.0.0.pre6 21 Dec 2015 none MIT — Details →
1.0.0.pre5 20 Dec 2015 none MIT — Details →
1.0.0.pre4 19 Dec 2015 none MIT — Details →
1.0.0.pre3 18 Dec 2015 none MIT — Details →
1.0.0.pre2 18 Dec 2015 none MIT — Details →
1.0.0.pre1 05 Dec 2015 none MIT — Details →
0.9.8 29 Sep 2015 none MIT — Details →
0.9.7 20 Sep 2015 none MIT — Details →
0.9.6 07 Sep 2015 none MIT — Details →
0.9.5 06 Sep 2015 none MIT — Details →
0.9.4 25 Aug 2015 none MIT — Details →
0.9.3 19 Aug 2015 none MIT — Details →
0.8.14 19 Aug 2015 none MIT — Details →
0.9.2 18 Aug 2015 none MIT — Details →
0.8.13 14 Aug 2015 none MIT — Details →
0.9.1 14 Aug 2015 none MIT — Details →
0.9.0 23 Jul 2015 none MIT — Details →
0.9.0.pre 22 Jul 2015 none MIT — Details →
0.8.12 26 May 2015 none MIT — Details →
0.8.11 23 May 2015 none MIT — Details →
0.8.10 14 May 2015 none MIT — Details →
0.8.9 11 May 2015 none MIT — Details →
0.8.8 09 May 2015 none MIT — Details →
0.8.7 08 May 2015 none MIT — Details →
0.8.6 08 May 2015 none MIT — Details →
0.8.5 06 May 2015 none MIT — Details →
0.8.4 23 Apr 2015 none MIT — Details →
0.8.3 07 Apr 2015 none MIT — Details →
0.8.2 06 Apr 2015 none MIT — Details →
0.8.1 02 Apr 2015 none MIT — Details →
0.8.0 01 Apr 2015 none MIT — Details →
0.8.0.pre5 31 Mar 2015 none MIT — Details →
0.7.4 31 Mar 2015 none MIT — Details →
0.8.0.pre4 29 Mar 2015 none MIT — Details →
0.8.0.pre3 28 Mar 2015 none MIT — Details →
0.8.0.pre2 28 Mar 2015 none MIT — Details →
0.8.0.pre 26 Mar 2015 none MIT — Details →
0.6.4 25 Mar 2015 M1 MIT Yes Details →
0.7.3 25 Mar 2015 none MIT — Details →
0.7.2 02 Mar 2015 M1 MIT Yes Details →
0.7.1 03 Jan 2015 M1 MIT Yes Details →
0.7.0 02 Jan 2015 M1 MIT Yes Details →
0.6.3 14 Nov 2014 M1 MIT Yes Details →
0.6.2 06 Aug 2014 M1 MIT Yes Details →
0.5.1 26 May 2014 M1 — Yes Details →
0.6.1 08 May 2014 M1 MIT Yes Details →
0.6.0 04 Apr 2014 M1 MIT Yes Details →
0.6.0.pre 29 Mar 2014 M1 MIT Yes Details →
0.5.0 14 Sep 2013 M1 — Yes Details →
0.5.0.pre2 11 Sep 2013 M1 — Yes Details →
0.5.0.pre 06 Sep 2013 M1 — Yes Details →
0.4.0 12 Oct 2012 M1 — Yes Details →
0.3.0 01 Sep 2012 M1 — Yes Details →
0.2.0 05 Mar 2012 M1 — Yes Details →
0.1.0 27 Jan 2012 M1 — Yes Details →
0.0.2 30 Nov 2011 M1 — Yes Details →
0.0.1 11 Oct 2011 M1 — Yes Details →
0.0.0 06 Oct 2011 M1 — Yes Details →

All 109 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for http

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-1828: Vulnerability in Ruby http Gem 5.9 medium 0.7.3 13 Mar 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About http

Is http safe to use?

Vulert records 1 vulnerabilities for http in RubyGems: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is http's Vulert package health score?

Vulert scores http 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of http affected?

No. 6.0.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of http should I use?

6.0.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does http have?

1 vulnerability is recorded for http in the RubyGems ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new http vulnerabilities disclosed?

0 vulnerabilities were recorded for http in the last 12 months, and the oldest entry in this database dates to 13 Mar 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of http are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor http for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the http version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.