Skip to main content
Mallory
MediumVulnerability

CVE-2023-32681: Proxy credential disclosure on HTTPS redirects in Python Requests

Published May 26, 2023 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS6.1Medium · v3.1
EPSS3.0%88th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Fedora ProjectPython
IdentifiersCVE-2023-32681CWE-200 · Exposure of Sensitive Information…

CVE-2023-32681 is an information disclosure vulnerability in the Python Requests HTTP library affecting versions 2.3.0 through versions before 2.31.0. During redirection to an HTTPS endpoint, the rebuild_proxies function incorrectly reattaches the Proxy-Authorization header to the destination request. HTTPS proxy authentication belongs in the CONNECT request, rather than inside the encrypted tunnel, where the proxy cannot inspect or remove the header. Consequently, the redirected destination server can receive sensitive proxy credentials intended only for the proxy.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A destination server receiving an affected redirected request can obtain proxy authentication credentials, compromising their confidentiality. Captured credentials could potentially be reused to authenticate to the proxy, subject to its authentication mechanism and access restrictions. The vulnerability has no identified direct integrity or availability impact.

Mitigation

If you can’t patch tonight, do this now.

Until the fix can be applied, prevent affected Requests clients from following redirects to HTTPS endpoints through authenticated proxies. Disabling automatic redirect following and rejecting such redirects avoids the vulnerable redirect-processing path.

Remediation

Patch, then assume compromise.

Upgrade Requests to version 2.31.0 or later, or install a vendor-supported package containing the backported fix. Update affected applications, bundled dependencies, and container images that include vulnerable Requests versions. For distribution-managed installations, apply the corresponding vendor security updates; Google Container-Optimized OS identifies dev-python/requests and related package version 18244.1.61 or later as fixed.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Fedora ProjectFedoraoperating_system
PythonRequestsapplication
FAQ

Frequently asked questions

Is CVE-2023-32681 exploited in the wild?
As of Nov 3, 2026, Mallory has no reports of CVE-2023-32681 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-32681?
As of Nov 3, 2026, Mallory has found no public exploit for CVE-2023-32681.
Is there a patch for CVE-2023-32681?
Upgrade Requests to version 2.31.0 or later, or install a vendor-supported package containing the backported fix. Update affected applications, bundled dependencies, and container images that include vulnerable Requests versions.
What products are affected by CVE-2023-32681?
Python Requests and Fedora Project Fedora.
How severe is CVE-2023-32681?
CVE-2023-32681 has a CVSS v3.1 score of 6.1 (Medium) and an EPSS score of 3.0% (88th percentile) as of Nov 3, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.