Search

Find a vulnerability

Search criteria

    Related vulnerabilities

    BREW-BUMP-MY-VERSION-CVE… (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 18:58 – Updated: 2026-10-26 09:35 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "bump-my-version",
            "purl": "pkg:brew/bump-my-version"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.4.0"
                },
                {
                  "fixed": "1.5.1_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-bump-my-version-CVE-2026-84382",
      "modified": "2026-10-26T09:35:16Z",
      "published": "2026-09-10T18:58:21Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-HATCH-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 19:26 – Updated: 2026-10-23 09:20 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "hatch",
            "purl": "pkg:brew/hatch"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.17.0"
                },
                {
                  "fixed": "1.18.0_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-hatch-CVE-2026-84382",
      "modified": "2026-10-23T09:20:47Z",
      "published": "2026-09-10T19:26:01Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-HERMES-AGENT-CVE-20… (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-10-04 11:46 – Updated: 2026-10-27 17:56 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.12.0",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "hermes-agent",
            "purl": "pkg:brew/hermes-agent"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.21.6"
                },
                {
                  "fixed": "0.22.2"
                }
              ],
              "type": "ECOSYSTEM"
            },
            {
              "events": [
                {
                  "introduced": "2026.8.31_1"
                },
                {
                  "last_affected": "2026.9.24"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.12.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.12.0"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-hermes-agent-CVE-2026-84382",
      "modified": "2026-10-27T17:56:27Z",
      "published": "2026-10-04T11:46:48Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-HTTPX2-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 19:29 – Updated: 2026-11-18 10:12 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "httpx2",
            "purl": "pkg:brew/httpx2"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "2.9.1"
                },
                {
                  "fixed": "2.12.0"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.2",
            "name": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.2"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-httpx2-CVE-2026-84382",
      "modified": "2026-11-18T10:12:49Z",
      "published": "2026-09-10T19:29:22Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-LITECLI-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 19:42 – Updated: 2026-10-12 17:50 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.13.1",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "litecli",
            "purl": "pkg:brew/litecli"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.17.1_3"
                },
                {
                  "fixed": "1.17.1_4"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.13.1",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.13.1"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-litecli-CVE-2026-84382",
      "modified": "2026-10-12T17:50:02Z",
      "published": "2026-09-10T19:42:52Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-OTERM-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 20:19 – Updated: 2026-10-23 08:59 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "oterm",
            "purl": "pkg:brew/oterm"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.19.0"
                },
                {
                  "fixed": "0.24.0"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-oterm-CVE-2026-84382",
      "modified": "2026-10-23T08:59:58Z",
      "published": "2026-09-10T20:19:30Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-PAPIS-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 20:21 – Updated: 2026-11-14 11:55 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "papis",
            "purl": "pkg:brew/papis"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.15.0_5"
                },
                {
                  "fixed": "0.16.0_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-papis-CVE-2026-84382",
      "modified": "2026-11-14T11:55:47Z",
      "published": "2026-09-10T20:21:27Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-RAPID-MLX-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 20:37 – Updated: 2026-11-19 10:42 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.2",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "rapid-mlx",
            "purl": "pkg:brew/rapid-mlx"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0.11.3"
                },
                {
                  "fixed": "0.12.16"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.2",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.2"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-rapid-mlx-CVE-2026-84382",
      "modified": "2026-11-19T10:42:42Z",
      "published": "2026-09-10T20:37:33Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-STRANDS-AGENTS-SOPS… (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 21:05 – Updated: 2026-11-15 10:04 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.16.0",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "strands-agents-sops",
            "purl": "pkg:brew/strands-agents-sops"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "1.1.3"
                },
                {
                  "fixed": "1.1.3_1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.16.0",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.16.0"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-strands-agents-sops-CVE-2026-84382",
      "modified": "2026-11-15T10:04:58Z",
      "published": "2026-09-10T21:05:20Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    BREW-YEWTUBE-CVE-2026-84382 (GHSA-8XX6-HGC6-GC2M)

    Vulnerability from osv_homebrew – Published: 2026-09-10 21:31 – Updated: 2026-10-04 22:23 – Source website
    VLAI
    Summary
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Details

    Summary

    When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.

    Details

    HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.

    At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.

    Impact

    Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.

    Mitigation

    Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.


    {
      "affected": [
        {
          "ecosystem_specific": {
            "fix": "bump",
            "range_state": "fixed",
            "resource": "httpx2",
            "resource_purl": "pkg:pypi/httpx2@2.13.1",
            "upstream_fixed_in": "2.12.0"
          },
          "package": {
            "ecosystem": "Homebrew",
            "name": "yewtube",
            "purl": "pkg:brew/yewtube"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "2.13.1_4"
                },
                {
                  "fixed": "2.13.1_5"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "database_specific": {
        "confidence": "high",
        "source": "matched",
        "strategy": "registry",
        "upstream_evidence": [
          {
            "ecosystem": "PyPI",
            "key": "pkg:pypi/httpx2@2.13.1",
            "name": "httpx2",
            "resource": "httpx2",
            "strategy": "registry",
            "subject_version": "2.13.1"
          }
        ]
      },
      "details": "### Summary\n\nWhen decoding a compressed response body (`gzip`, `deflate`, `br`, or `zstd`), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.\n\n### Details\n\nHTTPX2\u0027s default transport reads the socket in pieces of up to 64 KiB. Before `2.12.0`, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.\n\nAt DEFLATE\u0027s maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.\n\n### Impact\n\nApplications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.12.0` or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.",
      "id": "BREW-yewtube-CVE-2026-84382",
      "modified": "2026-10-04T22:23:47Z",
      "published": "2026-09-10T21:31:38Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
        },
        {
          "type": "ADVISORY",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84382"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/pull/1126"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
        },
        {
          "type": "PACKAGE",
          "url": "https://github.com/pydantic/httpx2"
        },
        {
          "type": "WEB",
          "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
        }
      ],
      "schema_version": "1.7.3",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "type": "CVSS_V3"
        }
      ],
      "summary": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)",
      "upstream": [
        "GHSA-8xx6-hgc6-gc2m",
        "CVE-2026-84382",
        "PYSEC-2026-3846"
      ]
    }

    CVE-2026-84382 (GCVE-0-2026-84382)

    Vulnerability from cvelistv5 – Published: 2026-09-02 18:03 – Updated: 2026-09-03 14:31
    VLAI
    Title
    HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
    Summary
    HTTPX2 is a next generation HTTP client for Python. Prior to 2.12.0, the HTTPX2 content decoders in src/httpx2/httpx2/_decoders.py fully inflate each gzip, deflate, br, or zstd network chunk before iter_bytes() or aiter_bytes() yields bounded pieces to the application. A 64 KiB compressed chunk can expand to approximately 64 MiB in one intermediate allocation, so an attacker-controlled or compromised server can cause severe memory pressure or out-of-memory process termination even when the application streams the response. This issue is fixed in version 2.12.0.
    SSVC
    Exploitation: none Automatable: yes Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-09-03 14:09 UTC
    CWE
    • CWE-409 - Improper Handling of Highly Compressed Data (Data Amplification)
    Assigner
    GitHub_M CNA
    Impacted products
    Vendor Product Version
    pydantic httpx2 Affected: < 2.12.0
    Create a notification for this product.
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-84382",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "yes"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-09-03T14:09:07.115167Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-09-03T14:31:19.366Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "httpx2",
              "vendor": "pydantic",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003c 2.12.0"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "HTTPX2 is a next generation HTTP client for Python. Prior to 2.12.0, the HTTPX2 content decoders in src/httpx2/httpx2/_decoders.py fully inflate each gzip, deflate, br, or zstd network chunk before iter_bytes() or aiter_bytes() yields bounded pieces to the application. A 64 KiB compressed chunk can expand to approximately 64 MiB in one intermediate allocation, so an attacker-controlled or compromised server can cause severe memory pressure or out-of-memory process termination even when the application streams the response. This issue is fixed in version 2.12.0."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-409",
                  "description": "CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-09-02T18:03:05.010Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m"
            },
            {
              "name": "https://github.com/pydantic/httpx2/pull/1126",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/pydantic/httpx2/pull/1126"
            },
            {
              "name": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8"
            },
            {
              "name": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/pydantic/httpx2/releases/tag/v2.12.0"
            }
          ],
          "source": {
            "advisory": "GHSA-8xx6-hgc6-gc2m",
            "discovery": "UNKNOWN"
          },
          "title": "HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2026-84382",
        "datePublished": "2026-09-02T18:03:05.010Z",
        "dateReserved": "2026-09-01T16:27:58.130Z",
        "dateUpdated": "2026-09-03T14:31:19.366Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }