# CVE-2025-32026: Element Web could load a malicious instance of Element Call leaking media encryption keys

> Attackers can leak media encryption keys if Element Web is configured to load Element Call from a malicious external URL.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-69q3-jg79-cg79

## What is CVE-2025-32026?

CVE-2025-32026 is a low-severity vulnerability in element-hq element-web, published on 8 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Element Web is a Matrix web client built using the Matrix React SDK. Element Web, starting from version 1.11.16 up to version 1.11.96, can be configured to load Element Call from an external URL. Under certain conditions, the external page is able to get access to the media encryption keys used for an Element Call call. Version 1.11.97 fixes the problem.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-32026 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32026 is a low-severity vulnerability in element-hq element-web, published on 8 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32026 in the wild and no public exploit code.

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

## Sources

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

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