⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.2

How to Fix CVE-2026-44431: Information Disclosure in urllib3

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.2 - High
Actively exploited?Not currently listed in CISA KEV
Affected>= 1.23, < 2.7.0
Fixed in2.7.0.
Type (CWE)CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

What is CVE-2026-44431?

CVE-2026-44431 is an information disclosure flaw in urllib3. The product returns sensitive data to a caller who should not have access, including credentials, session tokens, or configuration. Disclosure often feeds a follow-up attack chain. Vendor description: urllib3 is an HTTP client library for Python. From 1.23 to before 2.7.0, cross-origin redirects followed from the low-level API via ProxyManager.connection_from_url().urlopen(..., assert_same_host=False) still forward these sensitive headers.

Why this CVE matters

Information disclosure flaws are dangerous because they make the next attack easier. Sensitive configuration, session material, or credentials leaked from one endpoint frequently power the follow-on attack that actually takes over the system.

For deployments of urllib3 that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open urllib3's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-44431

  1. Read the vendor advisory in full: https://github.com/urllib3/urllib3/security/advisories/GHSA-qccp-gfcp-xxvc
  2. Upgrade urllib3 to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Update the Python package


# CVE-2026-44431 affects urllib3 >= 1.23, < 2.7.0. Fixed in 2.7.0.
# Vendor advisory: https://github.com/urllib3/urllib3/security/advisories/GHSA-qccp-gfcp-xxvc

# 1. Show the currently installed version.
python -m pip show urllib3 | grep -i version

# 2. Upgrade to the patched release.
python -m pip install --upgrade "urllib3>=2.7.0"

# 3. For projects pinned via requirements.txt, bump the pin and re-sync.
sed -i 's/^urllib3==.*/urllib3==2.7.0/' requirements.txt
python -m pip install -r requirements.txt

# 4. Verify.
python -m pip show urllib3 | grep -i version


# Same flow on Windows.
python -m pip install --upgrade "urllib3>=2.7.0"
python -m pip show urllib3

Verify the fix landed


# CVE-2026-44431 verification checklist.

# 1. Confirm the running version matches 2.7.0 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-44431.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://github.com/urllib3/urllib3/security/advisories/GHSA-qccp-gfcp-xxvc

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-44431 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-44431?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for urllib3 run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*