How severe is GHSA-jcr6-4frq-9gjj?

No CVSS score has been assigned to GHSA-jcr6-4frq-9gjj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jcr6-4frq-9gjj?

GHSA-jcr6-4frq-9gjj affects the following packages: users (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-jcr6-4frq-9gjj?

The records we use list no patched version of users for GHSA-jcr6-4frq-9gjj. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-jcr6-4frq-9gjj in my crates.io dependencies?

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

How do I mitigate GHSA-jcr6-4frq-9gjj 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.

Is GHSA-jcr6-4frq-9gjj actively exploited in the wild?

No public exploit code has been indexed for GHSA-jcr6-4frq-9gjj 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-jcr6-4frq-9gjj published, and has it been updated?

GHSA-jcr6-4frq-9gjj was published on September 11, 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

Users vulnerable to unaligned read of `const const c_char` pointerGHSA-jcr6-4frq-9gjj

GHSA-jcr6-4frq-9gjj is a security vulnerability in users. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2023-0059

Published

Sep 11, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀users

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 dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior.

In some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibility of working correctly in some architectures.

The crate is not currently maintained, so a patched version is not available.

Recommended alternatives

uzers (an actively maintained fork of the users crate)
sysinfo

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`users`	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 users, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of users for GHSA-jcr6-4frq-9gjj. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

Frequently Asked Questions

Affected versions dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior. In some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibility of working correctly in some architectures. The crate is not currently maintained, so a patched version is not available. ## Recommended alternatives - [`uzers`](https://crates.io/crates/uzers) (an actively maintained fork of the `users` crate) - [`sysinfo`](https://crates.io/crates/sysinfo)

O3 Security · Impact-Aware SCA

Is GHSA-jcr6-4frq-9gjj in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

Users vulnerable to unaligned read of `*const *const c_char` pointerGHSA-jcr6-4frq-9gjj