How severe is GHSA-x3f4-45xf-rjm7?

No CVSS score has been assigned to GHSA-x3f4-45xf-rjm7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x3f4-45xf-rjm7?

GHSA-x3f4-45xf-rjm7 affects the following packages: ruzstd (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-x3f4-45xf-rjm7?

Update ruzstd to 0.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3f4-45xf-rjm7 is resolved across your whole dependency graph.

How do I detect GHSA-x3f4-45xf-rjm7 in my crates.io dependencies?

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

How do I mitigate GHSA-x3f4-45xf-rjm7 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is GHSA-x3f4-45xf-rjm7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x3f4-45xf-rjm7 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-x3f4-45xf-rjm7 published, and has it been updated?

GHSA-x3f4-45xf-rjm7 was published on December 2, 2024 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

`ruzstd` uninit and out-of-bounds memory readsGHSA-x3f4-45xf-rjm7

Fix: KillingSpark/zstd-rs#76

GHSA-x3f4-45xf-rjm7 is a security vulnerability in ruzstd. A fix is available for ruzstd — see the affected versions and patch details below.

Also known asRUSTSEC-2024-0400

Published

Dec 2, 2024

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

🦀ruzstd

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 ruzstd miscalculate the length of the allocated and init section of its internal RingBuffer, leading to uninitialized or out-of-bounds reads in copy_bytes_overshooting of up to 15 bytes.

This may result in up to 15 bytes of memory contents being written into the decoded data when decompressing a crafted archive. This may occur multiple times per archive.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ruzstd`	≥ 0.7.0&&< 0.7.3	0.7.3`cargo update -p ruzstd --precise 0.7.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ruzstd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ruzstd to 0.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3f4-45xf-rjm7 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

Affected versions of `ruzstd` miscalculate the length of the allocated and init section of its internal `RingBuffer`, leading to uninitialized or out-of-bounds reads in `copy_bytes_overshooting` of up to 15 bytes. This may result in up to 15 bytes of memory contents being written into the decoded data when decompressing a crafted archive. This may occur multiple times per archive.

O3 Security · Impact-Aware SCA

Is GHSA-x3f4-45xf-rjm7 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works