How severe is GHSA-rc23-xxgq-x27g?

No CVSS score has been assigned to GHSA-rc23-xxgq-x27g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rc23-xxgq-x27g?

GHSA-rc23-xxgq-x27g affects the following packages: wee_alloc (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-rc23-xxgq-x27g?

The records we use list no patched version of wee_alloc for GHSA-rc23-xxgq-x27g. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-rc23-xxgq-x27g in my crates.io dependencies?

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

How do I mitigate GHSA-rc23-xxgq-x27g 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-rc23-xxgq-x27g actively exploited in the wild?

No public exploit code has been indexed for GHSA-rc23-xxgq-x27g 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-rc23-xxgq-x27g published, and has it been updated?

GHSA-rc23-xxgq-x27g was published on September 16, 2022 and was last updated on November 8, 2023. 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

wee_alloc is UnmaintainedGHSA-rc23-xxgq-x27g

GHSA-rc23-xxgq-x27g is a security vulnerability in wee_alloc. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2022-0054

Published

Sep 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀wee_alloc

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

Two of the maintainers have indicated that the crate may not be maintained.

The crate has open issues including memory leaks and may not be suitable for production use.

It may be best to switch to the default Rust standard allocator on wasm32 targets.

Last release seems to have been three years ago.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`wee_alloc`	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 wee_alloc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of wee_alloc for GHSA-rc23-xxgq-x27g. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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

Two of the maintainers have indicated that the crate may not be maintained. The crate has open issues including memory leaks and may not be suitable for production use. It may be best to switch to the default Rust standard allocator on wasm32 targets. Last release seems to have been three years ago.

O3 Security · Impact-Aware SCA

Is GHSA-rc23-xxgq-x27g in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works