How severe is GHSA-fjx5-qpf4-xjf2?

No CVSS score has been assigned to GHSA-fjx5-qpf4-xjf2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fjx5-qpf4-xjf2?

GHSA-fjx5-qpf4-xjf2 affects the following packages: borsh (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-fjx5-qpf4-xjf2?

Update borsh to 1.0.0-alpha.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fjx5-qpf4-xjf2 is resolved across your whole dependency graph.

How do I detect GHSA-fjx5-qpf4-xjf2 in my crates.io dependencies?

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

How do I mitigate GHSA-fjx5-qpf4-xjf2 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-fjx5-qpf4-xjf2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fjx5-qpf4-xjf2 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-fjx5-qpf4-xjf2 published, and has it been updated?

GHSA-fjx5-qpf4-xjf2 was published on April 17, 2023 and was last updated on September 23, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Parsing borsh messages with ZST which are…

Real-World Exposure

1 pkg affected

🦀borsh

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 borsh cause undefined behavior when zero-sized-types (ZST) are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy (this can be achieved through a singleton), then accessing/writing to deserialized data will cause a segmentation fault.

There is currently no way for borsh to read data without also providing a Rust type. Therefore, if you are not using ZST for serialization, then you are not affected by this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`borsh`	all versions	1.0.0-alpha.1`cargo update -p borsh --precise 1.0.0-alpha.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for borsh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update borsh to 1.0.0-alpha.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fjx5-qpf4-xjf2 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

Affected versions of borsh cause undefined behavior when zero-sized-types (ZST) are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy (this can be achieved through a singleton), then accessing/writing to deserialized data will cause a segmentation fault. There is currently no way for borsh to read data without also providing a Rust type. Therefore, if you are not using ZST for serialization, then you are not affected by this issue.

O3 Security · Impact-Aware SCA

Is GHSA-fjx5-qpf4-xjf2 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

Parsing borsh messages with ZST which are not-copy/clone is unsoundGHSA-fjx5-qpf4-xjf2