# CVE-2025-31126: Element X iOS allows the entity in control of the well-known file to break the confidentiality of embedded Element Call

> An attacker controlling the well-known file can access media encryption keys for Element Call, compromising call confidentiality.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2025
- **Updated:** 7 Apr 2025
- **Also known as:** GHSA-69qf-p24v-rf8j

## What is CVE-2025-31126?

CVE-2025-31126 is a medium-severity vulnerability in element-hq element-x-ios, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Element X iOS is a Matrix iOS Client provided by Element. In Element X iOS version between 1.6.13 and 25.03.7, the entity in control of the element.json well-known file is able, under certain conditions, to get access to the media encryption keys used for an Element Call call. This vulnerability is fixed in 25.03.8.

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

## Which versions are affected by CVE-2025-31126?


## How do I fix CVE-2025-31126?

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

## Is CVE-2025-31126 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31126 and fix it if it is affected.

What it is: CVE-2025-31126 is a medium-severity vulnerability in element-hq element-x-ios, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31126 in the wild and no public exploit code.

Affected product: element-hq element-x-ios. 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-2025-31126/ (Markdown: https://insights.sbomify.com/CVE-2025-31126/index.md)
```

## Sources

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

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