Is bugsnag/bugsnag-laravel 2.6 vulnerable?
Composer · 1 release from 2.6.0 to 2.6.0 · latest bugsnag/bugsnag-laravel is 2.31.0 · checked 18 Nov 2026
No known advisories in the last release
No. No bugsnag/bugsnag-laravel 2.6.x release has a known security advisory.
Is 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
Which of your client projects are still on bugsnag/bugsnag-laravel 2.6?
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.9
- bugsnag/bugsnag-laravel 2.8
- bugsnag/bugsnag-laravel 2.7
- bugsnag/bugsnag-laravel 2.5
- bugsnag/bugsnag-laravel 2.4
- bugsnag/bugsnag-laravel 2.3
- 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.