Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

GHSA-2c6h-4899-wjxr

scaly: Multiple soundness issues in Rust safe APIs

Also known asRUSTSEC-2026-0080
Published
Apr 4, 2026
Updated
Apr 5, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Blast Radius

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
EcosystemPackageVulnerable rangeFix
🦀crates.ioscalyall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scaly. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of scaly has shipped for GHSA-2c6h-4899-wjxr yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-2c6h-4899-wjxr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2c6h-4899-wjxr. 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 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?

O3 detects GHSA-2c6h-4899-wjxr across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.