How severe is GHSA-2c6h-4899-wjxr?

No CVSS score has been assigned to GHSA-2c6h-4899-wjxr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2c6h-4899-wjxr?

GHSA-2c6h-4899-wjxr affects the following packages: scaly (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2c6h-4899-wjxr?

The records we use list no patched version of scaly for GHSA-2c6h-4899-wjxr. 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-2c6h-4899-wjxr in my crates.io dependencies?

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

How do I mitigate GHSA-2c6h-4899-wjxr if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-2c6h-4899-wjxr actively exploited in the wild?

No public exploit code has been indexed for GHSA-2c6h-4899-wjxr 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-2c6h-4899-wjxr published, and has it been updated?

GHSA-2c6h-4899-wjxr was published on April 4, 2026 and was last updated on April 5, 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

scaly: Multiple soundness issues in Rust safe APIsGHSA-2c6h-4899-wjxr

GHSA-2c6h-4899-wjxr is a security vulnerability in scaly. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2026-0080

Published

Apr 4, 2026

Updated

Apr 5, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Apr 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀scaly

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 contain multiple safe APIs that can trigger undefined behavior:

Array<T>::index can perform an out-of-bounds read.
String::get_length can perform an out-of-bounds read.
String::append_character can perform an invalid write.
String::to_c_string can perform an out-of-bounds write.

These issues were reproduced against scaly 0.0.37 under Miri. The crate is unmaintained.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`scaly`	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 scaly, 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 scaly for GHSA-2c6h-4899-wjxr. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Affected versions contain multiple safe APIs that can trigger undefined behavior: - `Array<T>::index` can perform an out-of-bounds read. - `String::get_length` can perform an out-of-bounds read. - `String::append_character` can perform an invalid write. - `String::to_c_string` can perform an out-of-bounds write. These issues were reproduced against `scaly` 0.0.37 under Miri. The crate is unmaintained.

O3 Security · Impact-Aware SCA

Is GHSA-2c6h-4899-wjxr in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works