How severe is GHSA-w7hm-hmxv-pvhf?

GHSA-w7hm-hmxv-pvhf has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w7hm-hmxv-pvhf?

GHSA-w7hm-hmxv-pvhf affects the following packages: hpack (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-w7hm-hmxv-pvhf?

No patched version of hpack has shipped for GHSA-w7hm-hmxv-pvhf yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-w7hm-hmxv-pvhf in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hpack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w7hm-hmxv-pvhf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-w7hm-hmxv-pvhf actively exploited in the wild?

No public exploit code has been indexed for GHSA-w7hm-hmxv-pvhf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-w7hm-hmxv-pvhf published, and has it been updated?

GHSA-w7hm-hmxv-pvhf was published on April 5, 2024 and was last updated on April 11, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

HIGH severity

GHSA-w7hm-hmxv-pvhf — hpack

HIGHFix: sno2/hpack-rs-patched@d669282

GHSA-w7hm-hmxv-pvhf is a high-severity (CVSS 7.5) vulnerability in hpack. No vendor fix is recorded yet; mitigation options are listed below.

HPACK decoder panics on invalid input

Also known asRUSTSEC-2023-0085

Published

Apr 5, 2024

Updated

Apr 11, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Apr 11, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀hpack

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Due to insufficient checking of input data, decoding certain data sequences can lead to Decoder::decode panicking rather than returning an error.

Example code that triggers this vulnerability looks like this:

use hpack::Decoder;

pub fn main() {
  let input = &[0x3f];
  let mut decoder = Decoder::new();
  let _ = decoder.decode(input);
}

hpack is unmaintained. A crate with the panics fixed has been published as hpack-patched.

Also consider using fluke-hpack or httlib-huffman as an alternative.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hpack`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hpack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of hpack has shipped for GHSA-w7hm-hmxv-pvhf yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Due to insufficient checking of input data, decoding certain data sequences can lead to _Decoder::decode_ panicking rather than returning an error. Example code that triggers this vulnerability looks like this: ```rust use hpack::Decoder; pub fn main() { let input = &[0x3f]; let mut decoder = Decoder::new(); let _ = decoder.decode(input); } ``` hpack is unmaintained. A crate with the panics fixed has been published as [hpack-patched](https://crates.io/crates/hpack-patched). Also consider using [fluke-hpack](https://crates.io/crates/fluke-hpack) or [httlib-huffman](https://crates.io/

O3 Security · Impact-Aware SCA

Is GHSA-w7hm-hmxv-pvhf in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works