How severe is GHSA-585q-cm62-757j?

No CVSS score has been assigned to GHSA-585q-cm62-757j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-585q-cm62-757j?

GHSA-585q-cm62-757j affects the following packages: mnl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-585q-cm62-757j?

Update mnl to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-585q-cm62-757j is resolved across your whole dependency graph.

How do I detect GHSA-585q-cm62-757j in my crates.io dependencies?

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

How do I mitigate GHSA-585q-cm62-757j 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-585q-cm62-757j?

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

Is GHSA-585q-cm62-757j actively exploited in the wild?

No public exploit code has been indexed for GHSA-585q-cm62-757j 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-585q-cm62-757j published, and has it been updated?

GHSA-585q-cm62-757j was published on January 9, 2026 and was last updated on February 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-585q-cm62-757j — mnl

Fix: mullvad/mnl-rs#21

GHSA-585q-cm62-757j is a security vulnerability in mnl. A fix is available for mnl — see the affected versions and patch details below.

mnl has segmentation fault and invalid memory read in `mnl::cb_run`

Also known asRUSTSEC-2025-0142

Published

Jan 9, 2026

Updated

Feb 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀mnl

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

The function mnl::cb_run is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers.

Passing a crafted byte slice to mnl::cb_run can trigger memory violations. The function does not sufficiently validate the input buffer structure before processing, leading to out-of-bounds reads.

This vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`mnl`	all versions	0.3.1`cargo update -p mnl --precise 0.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mnl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mnl to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-585q-cm62-757j 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-585q-cm62-757j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-585q-cm62-757j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The function `mnl::cb_run` is marked as safe but exhibits unsound behavior when processing malformed Netlink message buffers. Passing a crafted byte slice to `mnl::cb_run` can trigger memory violations. The function does not sufficiently validate the input buffer structure before processing, leading to out-of-bounds reads. This vulnerability allows an attacker to cause a Denial of Service (segmentation fault) or potentially read unmapped memory by providing a malformed Netlink message.

O3 Security · Impact-Aware SCA

Is GHSA-585q-cm62-757j in your dependencies?

O3 Security finds GHSA-585q-cm62-757j 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