How severe is GHSA-f67m-9j94-qv9j?

No CVSS score has been assigned to GHSA-f67m-9j94-qv9j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f67m-9j94-qv9j?

GHSA-f67m-9j94-qv9j affects the following packages: hyper (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-f67m-9j94-qv9j?

Update hyper to 0.14.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f67m-9j94-qv9j is resolved across your whole dependency graph.

How do I detect GHSA-f67m-9j94-qv9j in my crates.io dependencies?

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

How do I mitigate GHSA-f67m-9j94-qv9j 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.

How does O3 Security protect against GHSA-f67m-9j94-qv9j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f67m-9j94-qv9j can be triaged on real exposure rather than presence alone.

Is GHSA-f67m-9j94-qv9j actively exploited in the wild?

No public exploit code has been indexed for GHSA-f67m-9j94-qv9j 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-f67m-9j94-qv9j published, and has it been updated?

GHSA-f67m-9j94-qv9j was published on June 16, 2022 and was last updated on September 10, 2026. 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

GHSA-f67m-9j94-qv9j — hyper

Fix: hyperium/hyper#2545

GHSA-f67m-9j94-qv9j is a security vulnerability in hyper. A fix is available for hyper — see the affected versions and patch details below.

Parser creates invalid uninitialized value

Also known asRUSTSEC-2022-0022

Published

Jun 16, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀hyper

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

Affected versions of this crate called mem::uninitialized() in the HTTP1 parser to create values of type httparse::Header (from the httparse crate). This is unsound, since Header contains references and thus must be non-null.

The flaw was corrected by avoiding the use of mem::uninitialized(), using MaybeUninit instead.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hyper`	all versions	0.14.12`cargo update -p hyper --precise 0.14.12`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hyper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hyper to 0.14.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f67m-9j94-qv9j is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f67m-9j94-qv9j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f67m-9j94-qv9j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of this crate called `mem::uninitialized()` in the HTTP1 parser to create values of type `httparse::Header` (from the `httparse` crate). This is unsound, since `Header` contains references and thus must be non-null. The flaw was corrected by avoiding the use of `mem::uninitialized()`, using `MaybeUninit` instead.

O3 Security · Impact-Aware SCA

Is GHSA-f67m-9j94-qv9j in your dependencies?

O3 Security finds GHSA-f67m-9j94-qv9j across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works