# CVE-2024-26132: Element Android can be asked to share internal files.

> A malicious app can force Element Android to share sensitive internal files, such as FCM tokens, to an arbitrary room.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-8wj9-cx7h-pvm4

## What is CVE-2024-26132?

CVE-2024-26132 is a medium-severity vulnerability in element-hq element-android, published on 20 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Element Android is an Android Matrix Client. A third-party malicious application installed on the same phone can force Element Android, version 0.91.0 through 1.6.12, to share files stored under the `files` directory in the application's private data directory to an arbitrary room. The impact of the attack is reduced by the fact that the databases stored in this folder are encrypted. However, it contains some other potentially sensitive information, such as the FCM token. Forks of Element Android which have set `android:exported="false"` in the `AndroidManifest.xml` file for the `IncomingShareActivity` activity are not impacted. This issue is fixed in Element Android 1.6.12. There is no known workaround to mitigate the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-26132?

It affects 1 product.


Products: Element Element.

## How do I fix CVE-2024-26132?

No fix has been published for CVE-2024-26132 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-26132 being exploited?

There is no known exploitation of CVE-2024-26132 in the wild and no public exploit code.

## Other vulnerabilities in element-hq element-android

- [CVE-2024-26131](https://insights.sbomify.com/CVE-2024-26131/): Element Android Intent Redirection (high 8.4)
- [CVE-2022-41904](https://insights.sbomify.com/CVE-2022-41904/): Element iOS is vulnerable due to missing decoration for events decrypted with untrusted Megolm sessions (medium 6.4)
- [CVE-2025-27606](https://insights.sbomify.com/CVE-2025-27606/): Element Android PIN autologout bypass (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26132 and fix it if it is affected.

What it is: CVE-2024-26132 is a medium-severity vulnerability in element-hq element-android, published on 20 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26132 in the wild and no public exploit code.

Affected product: element-hq element-android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26132/ (Markdown: https://insights.sbomify.com/CVE-2024-26132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26132
- OSV: https://osv.dev/vulnerability/CVE-2024-26132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26132/
Summaries are generated and may contain mistakes; the official description above is the record.