How severe is GHSA-79m9-55jc-p6mw?

No CVSS score has been assigned to GHSA-79m9-55jc-p6mw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-79m9-55jc-p6mw?

GHSA-79m9-55jc-p6mw affects the following packages: scanner (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-79m9-55jc-p6mw?

The records we use list no patched version of scanner for GHSA-79m9-55jc-p6mw. 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-79m9-55jc-p6mw in my crates.io dependencies?

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

How do I mitigate GHSA-79m9-55jc-p6mw 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-79m9-55jc-p6mw actively exploited in the wild?

No public exploit code has been indexed for GHSA-79m9-55jc-p6mw 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-79m9-55jc-p6mw published, and has it been updated?

GHSA-79m9-55jc-p6mw was published on May 7, 2025 and was last updated on October 28, 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

scanner has a Public API without sufficient bounds checkingGHSA-79m9-55jc-p6mw

Fix: pombredanne/scanner-rs#1

GHSA-79m9-55jc-p6mw is a security vulnerability in scanner. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0033

Published

May 7, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀scanner

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

Match::get() and Match::ptr() lack sufficient bounds checks, leading to potential out of bounds reads.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`scanner`	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 scanner, 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 scanner for GHSA-79m9-55jc-p6mw. 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

`Match::get()` and `Match::ptr()` lack sufficient bounds checks, leading to potential out of bounds reads.

O3 Security · Impact-Aware SCA

Is GHSA-79m9-55jc-p6mw in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works