MediumGHSA-j8r2-6x86-q33qCVE-2023-32681PYSEC-2023-74

Unintended leak of Proxy-Authorization header in requests

Published 22 May 2023 · Updated 10 Sept 2026

Is your project on an affected requests?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=2.3.0 <2.31.0
Fixed in
2.31.0
Update to the fixed version for your release line, for example:pip install 'requests>=2.31.0'

Details

Impact

Since Requests v2.3.0, Requests has been vulnerable to potentially leaking Proxy-Authorization headers to destination servers, specifically during redirects to an HTTPS origin. This is a product of how rebuild_proxies is used to recompute and reattach the `Proxy-Authorization` header to requests when redirected. Note this behavior has _only_ been observed to affect proxied requests when credentials are supplied in the URL user information component (e.g. https://username:password@proxy:8080).

Current vulnerable behavior(s):

1. HTTP → HTTPS: leak 2. HTTPS → HTTP: no leak 3. HTTPS → HTTPS: leak 4. HTTP → HTTP: no leak

For HTTP connections sent through the proxy, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the Proxy-Authorization header must be sent in the CONNECT request as the proxy has no visibility into further tunneled requests. This results in Requests forwarding the header to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate those credentials.

The reason this currently works for HTTPS connections in Requests is the Proxy-Authorization header is also handled by urllib3 with our usage of the ProxyManager in adapters.py with `proxy_manager_for`. This will compute the required proxy headers in proxy_headers and pass them to the Proxy Manager, avoiding attaching them directly to the Request object. This will be our preferred option going forward for default usage.

Patches

Starting in Requests v2.31.0, Requests will no longer attach this header to redirects with an HTTPS destination. This should have no negative impacts on the default behavior of the library as the proxy credentials are already properly being handled by urllib3's ProxyManager.

For users with custom adapters, this _may_ be potentially breaking if you were already working around this behavior. The previous functionality of rebuild_proxies doesn't make sense in any case, so we would encourage any users impacted to migrate any handling of Proxy-Authorization directly into their custom adapter.

Workarounds

For users who are not able to update Requests immediately, there is one potential workaround.

You may disable redirects by setting allow_redirects to False on all calls through Requests top-level APIs. Note that if you're currently relying on redirect behaviors, you will need to capture the 3xx response codes and ensure a new request is made to the redirect destination.

import requests
r = requests.get('http://github.com/', allow_redirects=False)

Credits

This vulnerability was discovered and disclosed by the following individuals.

Dennis Brinkrolf, Haxolot (https://haxolot.com/) Tobias Funke, (tobiasfunke93@gmail.com)

Is GHSA-j8r2-6x86-q33q in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected requests, and gives you the command that fixes it.

More advisories for requests

  • MediumCVE-2026-25645Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function · 25 Mar 2026
  • MediumCVE-2024-47081Requests vulnerable to .netrc credentials leak via malicious URLs · 9 Jun 2025
  • MediumCVE-2024-35195Requests `Session` object does not verify requests after making first request with verify=False · 20 May 2024
  • MediumCVE-2014-1829Exposure of Sensitive Information to an Unauthorized Actor in Requests · 17 May 2022
  • MediumCVE-2014-1830Exposure of Sensitive Information to an Unauthorized Actor in Requests · 14 May 2022
  • MediumCVE-2015-2296Python Requests Session Fixation · 13 May 2022
All 8 advisories for requests

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.