How severe is GHSA-qhj8-q5r6-8q6j?

No CVSS score has been assigned to GHSA-qhj8-q5r6-8q6j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qhj8-q5r6-8q6j?

GHSA-qhj8-q5r6-8q6j affects the following packages: matrix-sdk-base (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-qhj8-q5r6-8q6j?

Update matrix-sdk-base to 0.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhj8-q5r6-8q6j is resolved across your whole dependency graph.

How do I detect GHSA-qhj8-q5r6-8q6j in my crates.io dependencies?

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

How do I mitigate GHSA-qhj8-q5r6-8q6j 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-qhj8-q5r6-8q6j actively exploited in the wild?

No public exploit code has been indexed for GHSA-qhj8-q5r6-8q6j 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.

What is the EPSS score for GHSA-qhj8-q5r6-8q6j?

GHSA-qhj8-q5r6-8q6j has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-qhj8-q5r6-8q6j published, and has it been updated?

GHSA-qhj8-q5r6-8q6j was published on September 11, 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

GHSA-qhj8-q5r6-8q6j — matrix-sdk-base

Fix: matrix-org/matrix-rust-sdk#5635

GHSA-qhj8-q5r6-8q6j is a security vulnerability in matrix-sdk-base. A fix is available for matrix-sdk-base — see the affected versions and patch details below.

matrix-sdk-base: Panic in the `RoomMember::normalized_power_level()` method

Also known asCVE-2025-59047RUSTSEC-2025-0000RUSTSEC-2025-0065

Published

Sep 11, 2025

Updated

Sep 11, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qhj8-q5r6-8q6j.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀matrix-sdk-base

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

In matrix-sdk-base before 0.14.1, calling the RoomMember::normalized_power_level() method can cause a panic if a room member has a power level of Int::Min.

Patches

The issue is fixed in matrix-sdk-base 0.14.1.

Workarounds

The affected method isn’t used internally, so avoiding calling RoomMember::normalized_power_level() prevents the panic.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`matrix-sdk-base`	all versions	0.14.1`cargo update -p matrix-sdk-base --precise 0.14.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-sdk-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matrix-sdk-base to 0.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhj8-q5r6-8q6j 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.

Frequently Asked Questions

In matrix-sdk-base before 0.14.1, calling the `RoomMember::normalized_power_level()` method can cause a panic if a room member has a power level of `Int::Min`. ### Patches The issue is fixed in matrix-sdk-base 0.14.1. ### Workarounds The affected method isn’t used internally, so avoiding calling `RoomMember::normalized_power_level()` prevents the panic.

O3 Security · Impact-Aware SCA

Is GHSA-qhj8-q5r6-8q6j in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works