Is bugsnag/bugsnag-laravel 1.0 vulnerable?

Composer · 11 releases from 1.0.0 to 1.0.10 · latest bugsnag/bugsnag-laravel is 2.31.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. bugsnag/bugsnag-laravel 1.0.10, the last 1.0 release, is affected by 1 known security advisory (1 high), including CVE-2016-5385. Upgrade to 2.0.2 or later to fix all of them.

Upgrade with:composer require bugsnag/bugsnag-laravel:^2.0.2

Is your project on an affected bugsnag/bugsnag-laravel?

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 bugsnag/bugsnag-laravel 1.0.10

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

    HTTP Proxy header vulnerability

    Affected
    <2.0.2
    Fixed in
    2.0.2

Every bugsnag/bugsnag-laravel 1.0.x release

Affected: 1.0.0 to 1.0.10. Latest bugsnag/bugsnag-laravel: 2.31.0.

VersionKnown advisories
bugsnag/bugsnag-laravel 1.0.10CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.9CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.8CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.7CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.6CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.5CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.4CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.3CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.2CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.1CVE-2016-5385
bugsnag/bugsnag-laravel 1.0.0CVE-2016-5385

Which of your client projects are still on bugsnag/bugsnag-laravel 1.0?

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

Other bugsnag/bugsnag-laravel 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.