Is bugsnag/bugsnag-laravel 2.0 vulnerable?

Composer · 3 releases from 2.0.0 to 2.0.2 · latest bugsnag/bugsnag-laravel is 2.31.0 · checked 18 Nov 2026

No known advisories in the last release

bugsnag/bugsnag-laravel 2.0.2, the last 2.0 release, has no known advisories. 1 advisory affects earlier 2.0.x releases, so update to 2.0.2.

Update within 2.0: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

Fixed within 2.0.x, affecting earlier releases

  • 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 2.0.x release

Affected: 2.0.0 to 2.0.1. 2.0.2 is not affected. Latest bugsnag/bugsnag-laravel: 2.31.0.

VersionKnown advisories
bugsnag/bugsnag-laravel 2.0.2None
bugsnag/bugsnag-laravel 2.0.1CVE-2016-5385
bugsnag/bugsnag-laravel 2.0.0CVE-2016-5385

Which of your client projects are still on bugsnag/bugsnag-laravel 2.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.