Is padraic/humbug_get_contents 1.0 vulnerable?

Composer · 5 releases from 1.0.0 to 1.0.4 · latest padraic/humbug_get_contents is 1.1.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. padraic/humbug_get_contents 1.0.4, the last 1.0 release, is affected by 1 known security advisory (1 high), including CVE-2016-5385. Upgrade to 1.1.2 or later to fix all of them.

Upgrade with:composer require padraic/humbug_get_contents:^1.1.2

Is your project on an affected padraic/humbug_get_contents?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting padraic/humbug_get_contents 1.0.4

  • HighCVE-2016-5385GHSA-m6ch-gg5f-wxx37 Apr 2022

    HTTP Proxy header vulnerability

    Affected
    <1.1.2
    Fixed in
    1.1.2

Every padraic/humbug_get_contents 1.0.x release

Affected: 1.0.0 to 1.0.4. Latest padraic/humbug_get_contents: 1.1.2.

VersionKnown advisories
padraic/humbug_get_contents 1.0.4CVE-2016-5385
padraic/humbug_get_contents 1.0.3CVE-2016-5385
padraic/humbug_get_contents 1.0.2CVE-2016-5385
padraic/humbug_get_contents 1.0.1CVE-2016-5385
padraic/humbug_get_contents 1.0.0CVE-2016-5385

Which of your client projects are still on padraic/humbug_get_contents 1.0?

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

Other padraic/humbug_get_contents versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.