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

GHSA-2c6h-4899-wjxr — scaly

GHSA-2c6h-4899-wjxr is a security vulnerability in scaly. No vendor fix is recorded yet; mitigation options are listed below.

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
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
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2c6h-4899-wjxr can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-2c6h-4899-wjxr across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-2c6h-4899-wjxr: scaly | O3 Security