How severe is GHSA-7vjm-6qgq-3mrq?

No CVSS score has been assigned to GHSA-7vjm-6qgq-3mrq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7vjm-6qgq-3mrq?

GHSA-7vjm-6qgq-3mrq affects the following packages: shaman (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7vjm-6qgq-3mrq?

The records we use list no patched version of shaman for GHSA-7vjm-6qgq-3mrq. 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-7vjm-6qgq-3mrq in my crates.io dependencies?

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

How do I mitigate GHSA-7vjm-6qgq-3mrq 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-7vjm-6qgq-3mrq actively exploited in the wild?

No public exploit code has been indexed for GHSA-7vjm-6qgq-3mrq 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-7vjm-6qgq-3mrq published, and has it been updated?

GHSA-7vjm-6qgq-3mrq was published on November 3, 2025 and was last updated on November 4, 2025. 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

Shaman has soundness issues and is unmaintainedGHSA-7vjm-6qgq-3mrq

GHSA-7vjm-6qgq-3mrq is a security vulnerability in shaman. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0113

Published

Nov 3, 2025

Updated

Nov 4, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Nov 4, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀shaman

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

shaman::cryptoutil::write_u64v_le and other functions mentioned above cannot garantee memory safety of get_unchecked later if both length are zero.

shaman is unmaintained.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`shaman`	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 shaman, 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 shaman for GHSA-7vjm-6qgq-3mrq. 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

`shaman::cryptoutil::write_u64v_le` and other functions mentioned above cannot garantee memory safety of get_unchecked later if both length are zero. `shaman` is unmaintained.

O3 Security · Impact-Aware SCA

Is GHSA-7vjm-6qgq-3mrq in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works