No. Junglewise Threat Intelligence has no report of CVE-2016-5385 being exploited in the wild.
How severe is CVE-2016-5385?
Low severity, with a CVSS score of 3.1, published 7 April 2022.
Which products and versions are affected?
amphp/artax (Packagist) ECOSYSTEM:introduced=0,fixed=1.0.4; bugsnag/bugsnag-laravel (Packagist) ECOSYSTEM:introduced=0,fixed=2.0.2; drupal/core (Packagist) ECOSYSTEM:introduced=8.0,fixed=8.1.7; guzzlehttp/guzzle (Packagist) ECOSYSTEM:introduced=6,fixed=6.2.1; and 1 more.
Is there a fix for CVE-2016-5385?
Yes. amphp/artax (Packagist): upgrade to 1.0.4 or later; bugsnag/bugsnag-laravel (Packagist): upgrade to 2.0.2 or later; drupal/core (Packagist): upgrade to 8.1.7 or later; guzzlehttp/guzzle (Packagist): upgrade to 6.2.1 or later; padraic/humbug_get_contents (Packagist): upgrade to 1.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-5385?
Check whether you run amphp/artax (Packagist), bugsnag/bugsnag-laravel (Packagist), drupal/core (Packagist) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
amphp/artax (Packagist): upgrade to 1.0.4 or later
composer require amphp/artax:^1.0.4
bugsnag/bugsnag-laravel (Packagist): upgrade to 2.0.2 or later
composer require bugsnag/bugsnag-laravel:^2.0.2
drupal/core (Packagist): upgrade to 8.1.7 or later
composer require drupal/core:^8.1.7
guzzlehttp/guzzle (Packagist): upgrade to 6.2.1 or later
composer require guzzlehttp/guzzle:^6.2.1
padraic/humbug_get_contents (Packagist): upgrade to 1.1.2 or later