How severe is GHSA-p2q9-36vw-c468?

No CVSS score has been assigned to GHSA-p2q9-36vw-c468 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p2q9-36vw-c468?

GHSA-p2q9-36vw-c468 affects the following packages: olm-sys (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-p2q9-36vw-c468?

The records we use list no patched version of olm-sys for GHSA-p2q9-36vw-c468. 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-p2q9-36vw-c468 in my crates.io dependencies?

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

How do I mitigate GHSA-p2q9-36vw-c468 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-p2q9-36vw-c468 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p2q9-36vw-c468 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-p2q9-36vw-c468 published, and has it been updated?

GHSA-p2q9-36vw-c468 was published on September 3, 2024 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

olm-sys: wrapped library unmaintained, potentially vulnerableGHSA-p2q9-36vw-c468

GHSA-p2q9-36vw-c468 is a security vulnerability in olm-sys. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2024-0368

Published

Sep 3, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀olm-sys

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

After several cryptographic vulnerabilities in libolm were disclosed publicly, the Matrix Foundation has officially deprecated the library. olm-sys is a thin wrapper around libolm and is now deprecated and potentially vulnerable in kind.

Users of olm-sys and its higher-level abstraction, olm-rs, are highly encouraged to switch to vodozemac as soon as possible. It is the successor effort to libolm and is written in Rust.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`olm-sys`	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 olm-sys, 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 olm-sys for GHSA-p2q9-36vw-c468. 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

After several cryptographic vulnerabilities in `libolm` were disclosed publicly, the Matrix Foundation has [officially deprecated the library](https://matrix.org/blog/2024/08/libolm-deprecation/). `olm-sys` is a thin wrapper around `libolm` and is now deprecated and potentially vulnerable in kind. Users of `olm-sys` and its higher-level abstraction, `olm-rs`, are highly encouraged to switch to [`vodozemac`](https://crates.io/crates/vodozemac) as soon as possible. It is the successor effort to `libolm` and is written in Rust.

O3 Security · Impact-Aware SCA

Is GHSA-p2q9-36vw-c468 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works