How severe is GHSA-mrrw-grhq-86gf?

No CVSS score has been assigned to GHSA-mrrw-grhq-86gf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mrrw-grhq-86gf?

GHSA-mrrw-grhq-86gf affects the following packages: ascii (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-mrrw-grhq-86gf?

Update ascii to 0.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrrw-grhq-86gf is resolved across your whole dependency graph.

How do I detect GHSA-mrrw-grhq-86gf in my crates.io dependencies?

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

How do I mitigate GHSA-mrrw-grhq-86gf 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.

How does O3 Security protect against GHSA-mrrw-grhq-86gf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mrrw-grhq-86gf can be triaged on real exposure rather than presence alone.

Is GHSA-mrrw-grhq-86gf actively exploited in the wild?

No public exploit code has been indexed for GHSA-mrrw-grhq-86gf 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-mrrw-grhq-86gf published, and has it been updated?

GHSA-mrrw-grhq-86gf was published on February 28, 2023 and was last updated on July 16, 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

GHSA-mrrw-grhq-86gf — ascii

Fix: tomprogrammer/rust-ascii#63

GHSA-mrrw-grhq-86gf is a security vulnerability in ascii. A fix is available for ascii — see the affected versions and patch details below.

Ascii (crate) allows out-of-bounds array indexing in safe code

Also known asRUSTSEC-2023-0015

Published

Feb 28, 2023

Updated

Jul 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 16, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀ascii

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 version of this crate had implementation of From<&mut AsciiStr> for &mut [u8] and &mut str. This can result in out-of-bounds array indexing in safe code.

The flaw was corrected in commit 8a6c779 by removing those impls.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ascii`	≥ 0.7.0&&< 0.9.3	0.9.3`cargo update -p ascii --precise 0.9.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ascii, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ascii to 0.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrrw-grhq-86gf is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mrrw-grhq-86gf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mrrw-grhq-86gf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected version of this crate had implementation of `From<&mut AsciiStr>` for `&mut [u8]` and `&mut str`. This can result in out-of-bounds array indexing in safe code. The flaw was corrected in commit [8a6c779](https://github.com/tomprogrammer/rust-ascii/pull/63/commits/8a6c7798c202766bd57d70fb8d12739dd68fb9dc) by removing those impls.

O3 Security · Impact-Aware SCA

Is GHSA-mrrw-grhq-86gf in your dependencies?

O3 Security finds GHSA-mrrw-grhq-86gf 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