GHSA-6hr6-w5qg-qmwg: Medium severity pip/h2 vulnerability

Published Aug 6, 2026
·
Updated

Impact h2 <=4.4.0 accepts request header blocks containing more than one Host header, and forwards every Host header to the consuming application. Where the consumer downgrades HTTP/2 to HTTP/1.1, the resulting request carries two Host header lines, which is a request smuggling primitive (CWE-444).

Patches Patched and fixed in v4.4.1

Workarounds Users of the h2 library are advised to check and follow HTTP semantics best practices in their application code. h2 provides best effort sanity checks, but ultimately the calling code is responsible to ensure proper and safe usage of HTTP/2 as provided by h2, hyperframe, and hpack.

References Similar to the previously disclosed and fixed duplicate content-length issue.

Affected Software

1 affected componentFixes available
pip/h2<=4.4.0
4.4.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/h2 to a version that resolves this vulnerability.

    Fixed in 4.4.1
  2. Upgrade

    Upgrade h2 to a version that resolves this vulnerability.

    Fixed in 4.4.1
  3. Configuration

    In the application code that consumes HTTP/2 requests from h2, follow HTTP semantics best practices so requests do not contain multiple Host header lines. This prevents the request smuggling primitive described for cases where HTTP/2 is downgraded to HTTP/1.1.

    h2-based HTTP/2 consumer application Host header handling = Ensure exactly one Host header is present per request (no duplicate Host headers).

Event History

Aug 6, 2026
Advisory Published
via GitHub·09:53 PM
Data Sourced
via GitHub·09:53 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of GHSA-6hr6-w5qg-qmwg?

The severity of GHSA-6hr6-w5qg-qmwg is medium, rated at 5.3.

2

What is the impact of GHSA-6hr6-w5qg-qmwg?

GHSA-6hr6-w5qg-qmwg allows multiple Host headers, which can lead to HTTP request smuggling.

3

How do I fix GHSA-6hr6-w5qg-qmwg?

To fix GHSA-6hr6-w5qg-qmwg, upgrade to a version of h2 higher than 4.4.0 that addresses this issue.

4

Which software is affected by GHSA-6hr6-w5qg-qmwg?

GHSA-6hr6-w5qg-qmwg affects the h2 library used in Python's pip package manager.

5

What protocols are involved in GHSA-6hr6-w5qg-qmwg?

GHSA-6hr6-w5qg-qmwg involves both HTTP/2 and HTTP/1.1 protocols.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203