urllib3 2.7.0 compatibility — CVE-2026-44431 and CVE-2026-44432

[fred-gremlin]

Describe the bug

urllib3 2.7.0 was released on May 7 and fixes two vulnerabilities:

• CVE-2026-44431 (CVSS 8.2, High) — sensitive headers (Authorization, Cookie, Proxy-Authorization) not stripped on cross-origin redirects when using the low-level ProxyManager API path
• CVE-2026-44432 (CVSS 8.9, High) — decompression bomb via Brotli streaming API (CWE-409)

pyproject.toml currently caps urllib3 at <=2.6.3, which prevents the fix from being resolved:

"urllib3>=1.25.4,<=2.6.3",

Upstream botocore already merged the 2.7.0 bump in boto/botocore#3702 (May 12). The same port-and-lift pattern used in #9971 for 2.6.3 should apply here.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Patched dependencies are available to use.

Current Behavior

Unpatched dependencies are forced.

Reproduction Steps

Build file config.

Possible Solution

Upstream botocore already merged the 2.7.0 bump in boto/botocore#3702 (May 12). The same port-and-lift pattern used in #9971 for 2.6.3 should apply here.

Additional Information/Context

No response

CLI version used

2.30 +

Environment details (OS name and version, etc.)

linux/6.17.0-20-generic

[adev-code]

Thanks for reaching out @fred-gremlin. AWS CLI should not be impacted by CVE-2026-44431 or CVE-2026-44432 at runtime. CLI's HTTP layer disables redirects retries=Retry(False) and response decompression decode_content=False on the only urllib3 send path, and we don't use Brotli or drain_conn(), so neither CVE's exploit path is reachable.

Scanners may still flag the bundled urllib3 2.6.3, and we're looking into updating to clear those findings.