Files
plan2code/scripts/fixtures/deps/uv-0.13.7/audit.json
T
2026-11-13 23:28:59 -08:00

314 lines
30 KiB
JSON
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{
"schema": {
"version": "preview"
},
"summary": {
"audited_packages": 5,
"vulnerabilities": 15,
"adverse_statuses": 0
},
"vulnerabilities": [
{
"dependency": {
"name": "certifi",
"version": "2023.7.22"
},
"id": "GHSA-248v-346w-9cwc",
"display_id": "PYSEC-2024-230",
"aliases": [
"CVE-2024-39689",
"PYSEC-2024-230"
],
"summary": "Certifi removes GLOBALTRUST root certificate",
"description": "Certifi 2024.07.04 removes root certificates from \"GLOBALTRUST\" from the root store. These are in the process of being removed from Mozilla's trust store.\n\nGLOBALTRUST's root certificates are being removed pursuant to an investigation which identified \"long-running and unresolved compliance issues\". Conclusions of Mozilla's investigation can be found [here]( https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/XpknYMPO8dI).",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2024-39689",
"fix_versions": [
"2024.7.4"
],
"published": "2024-07-05T20:06:40Z",
"modified": "2026-09-10T03:50:15.994602411Z"
},
{
"dependency": {
"name": "certifi",
"version": "2023.7.22"
},
"id": "GHSA-6q48-6c7w-9gw2",
"display_id": "PYSEC-2026-4320",
"aliases": [
"PYSEC-2026-4320"
],
"summary": "certifi bundles emSign root CAs with compromised intermediate CA keys",
"description": "Certifi versions before 2026.10.18 include the `emSign ECC Root CA - G3` root certificate in their bundled CA store. Eight eMudhra intermediate CA certificates that chain to this root have compromised private keys and the CA has revoked them. \n\nAn attacker with one of the compromised keys can issue valid-looking certificates for any hostname. If the attacker is also on-path, they can intercept or modify TLS traffic from clients that trust the certifi bundle. Examples include `requests`, `urllib3` and `pip`, and the Python.org macOS installer.\n\nCertifi 2026.10.18 removed all emSign roots from the bundle. Certifi 2026.10.19 restored the emSign roots that are not affected. Upgrade to 2026.10.19 or later, and rebuild container images that vendor certifi.",
"link": "https://github.com/advisories/GHSA-6q48-6c7w-9gw2",
"fix_versions": [
"2026.10.18"
],
"published": "2026-10-20T21:41:50.722083Z",
"modified": "2026-10-30T14:00:02.590922333Z"
},
{
"dependency": {
"name": "idna",
"version": "3.4"
},
"id": "GHSA-jjg7-2v4v-x38h",
"display_id": "PYSEC-2024-60",
"aliases": [
"CVE-2024-3651",
"PYSEC-2024-60"
],
"summary": "Internationalized Domain Names in Applications (IDNA) vulnerable to denial of service from specially crafted inputs to idna.encode",
"description": "### Impact\nA specially crafted argument to the `idna.encode()` function could consume significant resources. This may lead to a denial-of-service.\n\n### Patches\nThe function has been refined to reject such strings without the associated resource consumption in version 3.7.\n\n### Workarounds\nDomain names cannot exceed 253 characters in length, if this length limit is enforced prior to passing the domain to the `idna.encode()` function it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.\n\n### References\n* https://huntr.com/bounties/93d78d07-d791-4b39-a845-cbfabc44aadb",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2024-3651",
"fix_versions": [
"3.7"
],
"published": "2024-04-11T21:32:40Z",
"modified": "2026-09-10T03:50:12.774088619Z"
},
{
"dependency": {
"name": "idna",
"version": "3.4"
},
"id": "GHSA-65pc-fj4g-8rjx",
"display_id": "PYSEC-2026-215",
"aliases": [
"CVE-2026-45409",
"PYSEC-2026-215"
],
"summary": "Internationalized Domain Names in Applications (IDNA): Specially crafted inputs to idna.encode() can bypass CVE-2024-3651 fix",
"description": "This is the same issue as CVE-2024-3651, however the original remediation in 2024 was not a complete fix. Payloads such as `\"\\u0660\" * N` or `\"\\u30fb\" * N + \"\\u6f22\"` utilize the `valid_contexto` function prior to length rejection, and for high values of `N` will take a long time to process.\n\n### Impact\nA specially crafted argument to the `idna.encode()` function could consume significant resources. This may lead to a denial-of-service.\n\n### Patches\nStarting in version 3.14, the function rejects long inputs as soon as practicable prior to any further processing to minimize resource consumption. In version 3.15, this approach was extended to lesser used alternate functions (i.e. per-label conversions and codec support).\n\n### Workarounds\nDomain names cannot exceed 253 characters in length, if this length limit is enforced prior to passing the domain to the `idna.encode()` function it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2026-45409",
"fix_versions": [
"3.15"
],
"published": "2026-05-19T14:34:32Z",
"modified": "2026-09-10T03:50:45.700124422Z"
},
{
"dependency": {
"name": "requests",
"version": "2.31.0"
},
"id": "GHSA-9hjg-9r4m-mvj7",
"display_id": "PYSEC-2026-1872",
"aliases": [
"CVE-2024-47081",
"PYSEC-2026-1872"
],
"summary": "Requests vulnerable to .netrc credentials leak via malicious URLs",
"description": "### Impact\n\nDue to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs.\n\n### Workarounds\nFor older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on your Requests Session ([docs](https://requests.readthedocs.io/en/latest/api/#requests.Session.trust_env)).\n\n### References\nhttps://github.com/psf/requests/pull/6965\nhttps://seclists.org/fulldisclosure/2025/Jun/2",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2024-47081",
"fix_versions": [
"2.32.4"
],
"published": "2025-06-09T19:06:08Z",
"modified": "2026-10-19T20:00:04.71611453Z"
},
{
"dependency": {
"name": "requests",
"version": "2.31.0"
},
"id": "GHSA-9wx4-h78v-vm56",
"display_id": "PYSEC-2026-1873",
"aliases": [
"CVE-2024-35195",
"PYSEC-2026-1873"
],
"summary": "Requests `Session` object does not verify requests after making first request with verify=False",
"description": "When using a `requests.Session`, if the first request to a given origin is made with `verify=False`, TLS certificate verification may remain disabled for all subsequent requests to that origin, even if `verify=True` is explicitly specified later.\n\nThis occurs because the underlying connection is reused from the session's connection pool, causing the initial TLS verification setting to persist for the lifetime of the pooled connection. As a result, applications may unintentionally send requests without certificate verification, leading to potential man-in-the-middle attacks and compromised confidentiality or integrity.\n\nThis behavior affects versions of `requests` prior to 2.32.0.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2024-35195",
"fix_versions": [
"2.32.0"
],
"published": "2024-05-20T20:15:00Z",
"modified": "2026-09-10T03:50:13.740879755Z"
},
{
"dependency": {
"name": "requests",
"version": "2.31.0"
},
"id": "GHSA-gc5v-m9x4-r6x2",
"display_id": "PYSEC-2026-2275",
"aliases": [
"CVE-2026-25645",
"PYSEC-2026-2275"
],
"summary": "Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function",
"description": "### Impact\nThe `requests.utils.extract_zipped_paths()` utility function uses a predictable filename when extracting files from zip archives into the system temporary directory. If the target file already exists, it is reused without validation. A local attacker with write access to the temp directory could pre-create a malicious file that would be loaded in place of the legitimate one.\n\n### Affected usages\n**Standard usage of the Requests library is not affected by this vulnerability.** Only applications that call `extract_zipped_paths()` directly are impacted.\n\n### Remediation\nUpgrade to at least Requests 2.33.0, where the library now extracts files to a non-deterministic location.\n\nIf developers are unable to upgrade, they can set `TMPDIR` in their environment to a directory with restricted write access.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2026-25645",
"fix_versions": [
"2.33.0"
],
"published": "2026-03-25T16:56:28Z",
"modified": "2026-09-10T03:50:39.207922076Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-qccp-gfcp-xxvc",
"display_id": "PYSEC-2026-141",
"aliases": [
"CVE-2026-44431",
"PYSEC-2026-141"
],
"summary": "urllib3: Sensitive headers forwarded across origins in proxied low-level redirects",
"description": "### Impact\n\nWhen following cross-origin redirects for requests made using urllib3’s high-level APIs, such as `urllib3.request()`, `PoolManager.request()`, and `ProxyManager.request()`, sensitive headers — `Authorization`, `Cookie`, and `Proxy-Authorization` (defined in `Retry.DEFAULT_REMOVE_HEADERS_ON_REDIRECT`) — are stripped by default, as expected.\n\nHowever, cross-origin redirects followed from the low-level API via `ProxyManager.connection_from_url().urlopen(..., assert_same_host=False)` still forward these sensitive headers.\n\n### Affected usage\n\nApplications and libraries using urllib3 versions earlier than 2.7.0 may be affected if they allow cross-origin redirects while making requests through `HTTPConnection.urlopen()` instances created via `ProxyManager.connection_from_url()`.\n\n### Remediation\n\nUpgrade to urllib3 version 2.7.0 or later, in which sensitive headers are stripped from redirects followed by `HTTPConnection`.\n\nIf upgrading is not immediately possible, avoid using this low-level redirect flow for cross-origin redirects. If appropriate for your use case, switch to `ProxyManager.request()`.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2026-44431",
"fix_versions": [
"2.7.0"
],
"published": "2026-05-11T14:51:20Z",
"modified": "2026-09-10T03:50:47.27276564Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-2xpw-w6gg-jr37",
"display_id": "PYSEC-2026-1994",
"aliases": [
"CVE-2025-66471",
"PYSEC-2026-1994"
],
"summary": "urllib3 streaming API improperly handles highly compressed data",
"description": "### Impact\n\nurllib3's [streaming API](https://urllib3.readthedocs.io/en/2.5.0/advanced-usage.html#streaming-and-i-o) is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.\n\nWhen streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP `Content-Encoding` header (e.g., `gzip`, `deflate`, `br`, or `zstd`). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.\n\nThe decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.\n\n\n### Affected usages\n\nApplications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.\n\n`stream()`, `read(amt=256)`, `read1(amt=256)`, `read_chunked(amt=256)`, `readinto(b)` are examples of `urllib3.HTTPResponse` method calls using the affected logic unless decoding is disabled explicitly.\n\n\n### Remediation\n\nUpgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.\n\nIf your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the `urllib3[brotli]` extra in the patched versions of urllib3.\n\n\n### Credits\n\nThe issue was reported by @Cycloctane.\nSupplemental information was provided by @stamparm during a security audit performed by [7ASecurity](https://7asecurity.com/) and facilitated by [OSTIF](https://ostif.org/).",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2025-66471",
"fix_versions": [
"2.6.0"
],
"published": "2025-12-05T18:15:54Z",
"modified": "2026-09-25T17:15:05.968189421Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-34jh-p97f-mpxf",
"display_id": "PYSEC-2026-1995",
"aliases": [
"CVE-2024-37891",
"PYSEC-2026-1995"
],
"summary": "urllib3's Proxy-Authorization request header isn't stripped during cross-origin redirects",
"description": "When using urllib3's proxy support with `ProxyManager`, the `Proxy-Authorization` header is only sent to the configured proxy, as expected.\n\nHowever, when sending HTTP requests *without* using urllib3's proxy support, it's possible to accidentally configure the `Proxy-Authorization` header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the `Proxy-Authorization` HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects.\n\nBecause this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the `Proxy-Authorization` header during cross-origin redirects to avoid the small chance that users are doing this on accident.\n\nUsers should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the `Proxy-Authorization` header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach.\n\n## Affected usages\n\nWe believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited:\n\n* Setting the `Proxy-Authorization` header without using urllib3's built-in proxy support.\n* Not disabling HTTP redirects.\n* Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin.\n\n## Remediation\n\n* Using the `Proxy-Authorization` header with urllib3's `ProxyManager`.\n* Disabling HTTP redirects using `redirects=False` when sending requests.\n* Not using the `Proxy-Authorization` header.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2024-37891",
"fix_versions": [
"1.26.19",
"2.2.2"
],
"published": "2024-06-17T21:37:20Z",
"modified": "2026-09-10T03:50:14.811193644Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-38jv-5279-wg99",
"display_id": "PYSEC-2026-1996",
"aliases": [
"CVE-2026-21441",
"PYSEC-2026-1996"
],
"summary": "Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)",
"description": "### Impact\n\nurllib3's [streaming API](https://urllib3.readthedocs.io/en/2.6.2/advanced-usage.html#streaming-and-i-o) is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.\n\nurllib3 can perform decoding or decompression based on the HTTP `Content-Encoding` header (e.g., `gzip`, `deflate`, `br`, or `zstd`). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.\n\nHowever, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).\n\n### Affected usages\n\nApplications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting `preload_content=False` when they do not disable redirects.\n\n\n### Remediation\n\nUpgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when `preload_content=False`.\n\nIf upgrading is not immediately possible, disable [redirects](https://urllib3.readthedocs.io/en/2.6.2/user-guide.html#retrying-requests) by setting `redirect=False` for requests to untrusted source.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2026-21441",
"fix_versions": [
"2.6.3"
],
"published": "2026-01-07T19:18:14Z",
"modified": "2026-09-10T03:50:32.562010895Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-gm62-xv2j-4w53",
"display_id": "PYSEC-2026-1998",
"aliases": [
"CVE-2025-66418",
"PYSEC-2026-1998"
],
"summary": "urllib3 allows an unbounded number of links in the decompression chain",
"description": "## Impact\n\nurllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., `Content-Encoding: gzip, zstd`).\n\nHowever, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.\n\n\n## Affected usages\n\nApplications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.\n\n\n## Remediation\n\nUpgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.\n\nIf upgrading is not immediately possible, use [`preload_content=False`](https://urllib3.readthedocs.io/en/2.5.0/advanced-usage.html#streaming-and-i-o) and ensure that `resp.headers[\"content-encoding\"]` contains a safe number of encodings before reading the response content.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2025-66418",
"fix_versions": [
"2.6.0"
],
"published": "2025-12-05T18:15:19Z",
"modified": "2026-09-10T03:50:58.741847479Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-pq67-6m6q-mj2v",
"display_id": "PYSEC-2026-1999",
"aliases": [
"CVE-2025-50181",
"PYSEC-2026-1999"
],
"summary": "urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation",
"description": "urllib3 handles redirects and retries using the same mechanism, which is controlled by the `Retry` object. The most common way to disable redirects is at the request level, as follows:\n\n```python\nresp = urllib3.request(\"GET\", \"https://httpbin.org/redirect/1\", redirect=False)\nprint(resp.status)\n# 302\n```\n\nHowever, it is also possible to disable redirects, for all requests, by instantiating a `PoolManager` and specifying `retries` in a way that disable redirects:\n\n```python\nimport urllib3\n\nhttp = urllib3.PoolManager(retries=0) # should raise MaxRetryError on redirect\nhttp = urllib3.PoolManager(retries=urllib3.Retry(redirect=0)) # equivalent to the above\nhttp = urllib3.PoolManager(retries=False) # should return the first response\n\nresp = http.request(\"GET\", \"https://httpbin.org/redirect/1\")\n```\n\nHowever, the `retries` parameter is currently ignored, which means all the above examples don't disable redirects.\n\n## Affected usages\n\nPassing `retries` on `PoolManager` instantiation to disable redirects or restrict their number.\n\nBy default, requests and botocore users are not affected.\n\n## Impact\n\nRedirects are often used to exploit SSRF vulnerabilities. An application attempting to mitigate SSRF or open redirect vulnerabilities by disabling redirects at the PoolManager level will remain vulnerable.\n\n## Remediation\n\nYou can remediate this vulnerability with the following steps:\n\n * Upgrade to a patched version of urllib3. If your organization would benefit from the continued support of urllib3 1.x, please contact [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com) to discuss sponsorship or contribution opportunities.\n * Disable redirects at the `request()` level instead of the `PoolManager()` level.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2025-50181",
"fix_versions": [
"2.5.0"
],
"published": "2025-06-18T17:50:00Z",
"modified": "2026-09-10T03:50:25.299291456Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-8988-9cw3-xx77",
"display_id": "PYSEC-2026-4175",
"aliases": [
"CVE-2026-97687",
"PYSEC-2026-4175"
],
"summary": "urllib3: HTTPS proxy TLS configuration may be ignored or overridden",
"description": "## Impact\n\nurllib3 supports configuring TLS independently for an HTTPS proxy and the target server.\n\n`proxy_ssl_context`, `proxy_assert_hostname`, and `proxy_assert_fingerprint` configure the TLS connection to the proxy. `ssl_context` and the other target-specific TLS parameters configure the connection to the target server.\n\nIn urllib3 versions 1.26.0 through 2.7.0, these configurations were not consistently separated. Depending on the proxy mode, urllib3 could:\n\n1. Ignore `proxy_ssl_context` and use the target server's SSL context for the TLS connection to an HTTPS forwarding proxy.\n2. Override the HTTPS proxy's certificate-verification policy with the target server's certificate-verification policy.\n3. Apply target-specific SNI, hostname assertions, certificate fingerprint assertions, or TLS client credentials to the TLS connection to an HTTPS forwarding proxy.\n\nIn particular, configuring `cert_reqs=\"CERT_NONE\"` for a target server could overwrite the `verify_mode` of the SSL context configured for the HTTPS proxy. This modification occurred in place and persisted on the context object, potentially disabling proxy certificate verification for later connections that reused the same context.\n\nAn attacker able to intercept the connection to an HTTPS proxy may be able to impersonate the proxy when the effective proxy TLS configuration disables certificate verification or otherwise accepts the attacker's certificate. This may occur, for example, when the target server's trust or identity policy is incorrectly applied to the proxy connection.\n\nWhen HTTPS forwarding is enabled, an impersonated proxy can observe or modify forwarded requests and responses, potentially exposing credentials, authentication tokens, request bodies, response data, and other sensitive information.\n\nA TLS client certificate intended for the target server may also be presented to the proxy or to an attacker impersonating it. This can disclose the client's identity and provide proof of possession of the corresponding private key. The private key itself is not transmitted during the TLS handshake.\n\nIn CONNECT tunneling mode, impersonating the HTTPS proxy does not by itself defeat the separate end-to-end TLS connection between the client and the target server.\n\n## Affected Usages\n\nCode using urllib3 versions 1.26.0 through 2.7.0 may be affected in any of the following cases.\n\n### 1. The target SSL context is used for an HTTPS forwarding proxy\n\nHTTPS requests are forwarded through an HTTPS proxy with `use_forwarding_for_https=True`, and `proxy_ssl_context` is configured for the proxy.\n\nurllib3 may ignore `proxy_ssl_context` and use the target server's `ssl_context` for the proxy TLS handshake. The proxy may therefore be verified using the target server's trust and certificate policy instead of the policy explicitly configured for the proxy.\n\n### 2. The target verification policy overrides the proxy policy\n\nAn HTTPS proxy is configured with `proxy_ssl_context`, while the target server uses a different certificate-verification policy.\n\nurllib3 may apply the target server's `cert_reqs` value to the proxy SSL context. For example, setting `cert_reqs=\"CERT_NONE\"` for the target server may also disable certificate verification for the HTTPS proxy, even when `proxy_ssl_context` was configured to require verification.\n\nThis issue can affect the TLS connection to an HTTPS proxy in both forwarding and CONNECT tunneling configurations.\n\n### 3. A mutated proxy SSL context is reused\n\nThe same SSL context is reused as `proxy_ssl_context` across multiple connections, and certificate verification is disabled for one target server.\n\nurllib3 may modify the proxy SSL context's `verify_mode` in place. Later connections that reuse the same context may therefore connect to the HTTPS proxy without certificate verification.\n\n### 4. Target-specific TLS identity or credentials are applied to the proxy\n\nHTTPS requests are forwarded through an HTTPS proxy with `use_forwarding_for_https=True`, and target-specific SNI, hostname assertions, certificate fingerprint assertions, or TLS client credentials are configured.\n\nurllib3 may apply these target-specific settings to the proxy TLS handshake. This may cause urllib3 to:\n\n- send SNI intended for the target server to the proxy;\n- verify the proxy using a hostname or certificate fingerprint intended for the target server; or\n- present a TLS client certificate intended for the target server to the proxy.\n\nCode connecting through a plain HTTP proxy does not establish a TLS connection to the proxy and is not affected by this issue.\n\n## Remediation\n\nUpgrade to urllib3 2.8.0 or later.\n\nurllib3 2.8.0 independently applies the explicitly configured `proxy_ssl_context` and proxy-specific certificate assertions to the HTTPS proxy connection. Target-specific SNI, certificate assertions, and TLS client certificate parameters are no longer applied to the HTTPS proxy handshake.\n\nFor backward compatibility, when an HTTPS proxy is used with `use_forwarding_for_https=True` and `proxy_ssl_context` is not provided, urllib3 2.8.0 continues to use `ssl_context` for the TLS connection to the proxy. This configuration emits a `FutureWarning`. In urllib3 3.0, passing `ssl_context` with `use_forwarding_for_https=True` for an HTTPS proxy will raise an error. Applications should use `proxy_ssl_context` to configure TLS for an HTTPS forwarding proxy.\n\nThe fixes were implemented in commits b6447295fff7b38fdffc67e0df9712d60cef3cc3 and 07408cec79d1856d81bb42c74a904a24fdb9e465.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2026-97687",
"fix_versions": [
"2.8.0"
],
"published": "2026-09-30T14:46:04Z",
"modified": "2026-10-01T17:55:53.79360855Z"
},
{
"dependency": {
"name": "urllib3",
"version": "1.26.18"
},
"id": "GHSA-vxq7-64xx-v4gw",
"display_id": "PYSEC-2026-4177",
"aliases": [
"CVE-2026-97689",
"PYSEC-2026-4177"
],
"summary": "urllib3: HTTPResponse.stream()/read_chunked() buffers an unbounded chunk-size line into memory",
"description": "## Impact\n\nurllib3's [streaming API](https://urllib3.readthedocs.io/en/2.7.0/advanced-usage.html#streaming-and-i-o) is designed for efficiently handling large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once. When decoding a [chunked-transfer-encoded response](https://httpwg.org/specs/rfc9112.html#chunked.encoding), this API reads each chunk's size field by buffering until it sees `\\n` or EOF.\n\nA malicious HTTP server can return `Transfer-Encoding: chunked` and then send a very long run of bytes without any newline, causing the streaming client to buffer that entire run before urllib3 can reject the chunk size as invalid and allocate more memory than intended.\n\nTo fix the issue, we'll reject chunk-size fields larger than 65536 bytes, as already done in the non-streaming case, which is currently handled by the Python standard library. Note that this only applies to reading the chunk-size field, not the chunk data, which is already handled correctly. Thus, there shouldn't be any impact for non-malicious servers.\n\n## Affected usages\n\nApplications and libraries using urllib3 versions earlier than 2.8.0 may be affected when streaming a chunked response from untrusted sources. Specifically, this affects the [read_chunked()](https://urllib3.readthedocs.io/en/stable/reference/urllib3.response.html#urllib3.response.BaseHTTPResponse.read_chunked) and [stream()](https://urllib3.readthedocs.io/en/stable/reference/urllib3.response.html#urllib3.response.BaseHTTPResponse.stream) methods of the HTTPResponse object.\n\nThis also affects requests streaming API, which uses urllib3 under the hood.\n\n## Remediation\n\nUpgrade to urllib3 version 2.8.0 or later, where chunk-size fields larger than 65536 will be rejected. If upgrading is not immediately possible, consider reading the response at once using the [read()](https://urllib3.readthedocs.io/en/stable/reference/urllib3.response.html#urllib3.response.BaseHTTPResponse.read) method.",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2026-97689",
"fix_versions": [
"2.8.0"
],
"published": "2026-09-30T14:46:18Z",
"modified": "2026-10-01T17:55:57.514829071Z"
}
],
"adverse_statuses": []
}