Advisories
This weekExploitable · Confirmed

guzzlehttp/guzzle, drupal/core: HTTP Proxy header vulnerability

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • guzzlehttp/guzzle (Packagist): from 6, before 6.2.1
  • guzzlehttp/guzzle (Packagist): from 4.0.0-rc2, before 4.2.4
  • guzzlehttp/guzzle (Packagist): from 5, before 5.3.1
  • drupal/core (Packagist): from 8.0, before 8.1.7
  • bugsnag/bugsnag-laravel (Packagist): every version, before 2.0.2
  • amphp/artax (Packagist): every version, before 1.0.4
  • amphp/artax (Packagist): from 2.0.0, before 2.0.4
  • padraic/humbug_get_contents (Packagist): every version, before 1.1.2

The fix

  • guzzlehttp/guzzle (Packagist) fixed in 6.2.1

    composer
    composer require "guzzlehttp/guzzle:^6.2.1" --update-with-all-dependencies
    Check what is installed
    composer show guzzlehttp/guzzle
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency guzzlehttp/guzzle to 6.2.1 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • guzzlehttp/guzzle (Packagist) fixed in 4.2.4

    composer
    composer require "guzzlehttp/guzzle:^4.2.4" --update-with-all-dependencies
    Check what is installed
    composer show guzzlehttp/guzzle
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency guzzlehttp/guzzle to 4.2.4 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • guzzlehttp/guzzle (Packagist) fixed in 5.3.1

    composer
    composer require "guzzlehttp/guzzle:^5.3.1" --update-with-all-dependencies
    Check what is installed
    composer show guzzlehttp/guzzle
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency guzzlehttp/guzzle to 5.3.1 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • drupal/core (Packagist) fixed in 8.1.7

    composer
    composer require "drupal/core:^8.1.7" --update-with-all-dependencies
    Check what is installed
    composer show drupal/core
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency drupal/core to 8.1.7 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • bugsnag/bugsnag-laravel (Packagist) fixed in 2.0.2

    composer
    composer require "bugsnag/bugsnag-laravel:^2.0.2" --update-with-all-dependencies
    Check what is installed
    composer show bugsnag/bugsnag-laravel
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency bugsnag/bugsnag-laravel to 2.0.2 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • amphp/artax (Packagist) fixed in 1.0.4

    composer
    composer require "amphp/artax:^1.0.4" --update-with-all-dependencies
    Check what is installed
    composer show amphp/artax
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency amphp/artax to 1.0.4 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • amphp/artax (Packagist) fixed in 2.0.4

    composer
    composer require "amphp/artax:^2.0.4" --update-with-all-dependencies
    Check what is installed
    composer show amphp/artax
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency amphp/artax to 2.0.4 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • padraic/humbug_get_contents (Packagist) fixed in 1.1.2

    composer
    composer require "padraic/humbug_get_contents:^1.1.2" --update-with-all-dependencies
    Check what is installed
    composer show padraic/humbug_get_contents
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency padraic/humbug_get_contents to 1.1.2 or the nearest later release, to fix CVE-2016-5385. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

  • Exploitable · Confirmed

    EPSS puts the chance of exploitation in the next 30 days at 50%.

    FIRST EPSSStated

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)