Is bugsnag/bugsnag-laravel 1.7 vulnerable?
Composer · 1 release from 1.7.0 to 1.7.0 · latest bugsnag/bugsnag-laravel is 2.31.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. bugsnag/bugsnag-laravel 1.7.0, the last 1.7 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.
composer require bugsnag/bugsnag-laravel:^2.0.2Is your project on an affected bugsnag/bugsnag-laravel?
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.7.0
HTTP Proxy header vulnerability
- Affected
- <2.0.2
- Fixed in
- 2.0.2
Which of your client projects are still on bugsnag/bugsnag-laravel 1.7?
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
- bugsnag/bugsnag-laravel 2.2
- bugsnag/bugsnag-laravel 2.1
- bugsnag/bugsnag-laravel 2.0
- bugsnag/bugsnag-laravel 1.6
- bugsnag/bugsnag-laravel 1.5
- bugsnag/bugsnag-laravel 1.4
- bugsnag/bugsnag-laravel 2.31
- bugsnag/bugsnag-laravel 2.30
- bugsnag/bugsnag-laravel 2.29
- bugsnag/bugsnag-laravel 2.28
- bugsnag/bugsnag-laravel 2.27
- bugsnag/bugsnag-laravel 2.26
- All bugsnag/bugsnag-laravel advisories
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.