GHSA-jjmc-4p83-pp26 — matrix-android-sdk2
MEDIUMGHSA-jjmc-4p83-pp26 is a medium-severity (CVSS 5.9) CWE-290 vulnerability in org.matrix.android:matrix-android-sdk2. A fix is available for org.matrix.android:matrix-android-sdk2 — see the affected versions and patch details below.
Logic error in Matrix SDK for Android
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-jjmc-4p83-pp26 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.matrix.android:matrix-android-sdk2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A logic error in the room key sharing functionality of Element Android before 1.2.2 and matrix-android-sdk2 (aka Matrix SDK for Android) before 1.2.2 leads to a situation where identity verification is inadequate and thus a key-requesting device can be impersonated.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.matrix.android:matrix-android-sdk2 | all versions | 1.2.2org.matrix.android:matrix-android-sdk2:1.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.matrix.android:matrix-android-sdk2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.matrix.android:matrix-android-sdk2 to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjmc-4p83-pp26 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-jjmc-4p83-pp26 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jjmc-4p83-pp26. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jjmc-4p83-pp26 in your dependencies?
O3 Security finds GHSA-jjmc-4p83-pp26 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.