How severe is GHSA-g98v-hv3f-hcfr?

No CVSS score has been assigned to GHSA-g98v-hv3f-hcfr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g98v-hv3f-hcfr?

GHSA-g98v-hv3f-hcfr affects the following packages: atty (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-g98v-hv3f-hcfr?

No patched version of atty has shipped for GHSA-g98v-hv3f-hcfr yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-g98v-hv3f-hcfr in my crates.io dependencies?

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

How do I mitigate GHSA-g98v-hv3f-hcfr 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-g98v-hv3f-hcfr?

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

Is GHSA-g98v-hv3f-hcfr actively exploited in the wild?

No public exploit code has been indexed for GHSA-g98v-hv3f-hcfr 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-g98v-hv3f-hcfr published, and has it been updated?

GHSA-g98v-hv3f-hcfr was published on June 30, 2023 and was last updated on September 10, 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-g98v-hv3f-hcfr — atty

Fix: softprops/atty#51

GHSA-g98v-hv3f-hcfr is a security vulnerability in atty. No vendor fix is recorded yet; mitigation options are listed below.

atty potential unaligned read

Also known asRUSTSEC-2021-0145

Published

Jun 30, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀atty

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

On windows, atty dereferences a potentially unaligned pointer.

In practice however, the pointer won't be unaligned unless a custom global allocator is used.

In particular, the System allocator on windows uses HeapAlloc, which guarantees a large enough alignment.

atty is Unmaintained

A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.

Last release of atty was almost 3 years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

std::io::IsTerminal - Stable since Rust 1.70.0
is-terminal - Standalone crate supporting Rust older than 1.70.0"

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`atty`	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 atty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of atty has shipped for GHSA-g98v-hv3f-hcfr yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g98v-hv3f-hcfr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g98v-hv3f-hcfr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

On windows, `atty` dereferences a potentially unaligned pointer. In practice however, the pointer won't be unaligned unless a custom global allocator is used. In particular, the `System` allocator on windows uses `HeapAlloc`, which guarantees a large enough alignment. # atty is Unmaintained A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable. Last release of `atty` was almost 3 years ago. ## Possible Alternative(s) The below list has not been vetted in any way and may or may not contain alternatives; - [std::io::IsTerminal](https://doc

O3 Security · Impact-Aware SCA

Is GHSA-g98v-hv3f-hcfr in your dependencies?

O3 Security finds GHSA-g98v-hv3f-hcfr 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