# CVE-2026-119407: Element Web and Element Desktop before 1.12.32 Forced Logout via Guest Credential URL Parameters


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-c88w-7h6p-27xr, GHSA-fm3q-8qwm-p5xr

## What is CVE-2026-119407?

CVE-2026-119407 is a high-severity vulnerability in element-hq element-desktop, published on 30 Oct 2026. 

### Official description

Element Web and Element Desktop before 1.12.32 accept guest credentials from URL fragment parameters in loadSession, allowing remote unauthenticated attackers to log out users and clear local stores. Attackers can lure logged-in users into opening links with guest_user_id and guest_access_token to force an attacker-controlled guest session and destroy unbacked end-to-end encryption keys.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-119407?


## How do I fix CVE-2026-119407?

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

## Is CVE-2026-119407 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119407 and fix it if it is affected.

What it is: CVE-2026-119407 is a high-severity vulnerability in element-hq element-desktop, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119407 in the wild and no public exploit code.

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

## Sources

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

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