# GHSA-2c6h-4899-wjxr: Multiple soundness issues in `scaly` safe APIs

> Safe APIs in the unmaintained scaly Rust library allow out-of-bounds reads and writes, potentially leading to memory corruption or crashes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2026
- **Also known as:** RUSTSEC-2026-0080

## What is GHSA-2c6h-4899-wjxr?

GHSA-2c6h-4899-wjxr is a memory corruption vulnerability in scaly, published on 19 Jan 2026. 

### Official 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. And the crate is unmaintained.

## Which versions are affected by GHSA-2c6h-4899-wjxr?

3 open source packages ship an affected version, including scaly.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `scaly` | crates.io | All versions to 0.0.37 | None |
| `scaly` | crates.io | All versions to 0.0.37 | None |
| `scaly` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for GHSA-2c6h-4899-wjxr yet. Limit exposure of the affected software until one is available.

## Is GHSA-2c6h-4899-wjxr being exploited?

There is no known exploitation of GHSA-2c6h-4899-wjxr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2c6h-4899-wjxr and fix it if it is affected.

What it is: GHSA-2c6h-4899-wjxr is a memory corruption vulnerability in scaly, published on 19 Jan 2026. 
Exploitation: There is no known exploitation of GHSA-2c6h-4899-wjxr in the wild and no public exploit code.

Affected packages and fixed versions:
- scaly (crates.io): affected all versions up to 0.0.37; no fix listed
- scaly (crates.io): affected all versions up to 0.0.37; no fix listed
- scaly (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-2c6h-4899-wjxr/ (Markdown: https://insights.sbomify.com/GHSA-2c6h-4899-wjxr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2c6h-4899-wjxr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2c6h-4899-wjxr/
Summaries are generated and may contain mistakes; the official description above is the record.