# CVE-2026-92839: Cross-site scripting in Canva

> An attacker can execute arbitrary same-origin content in Canva Desktop via double decoding in the deeplink handler, potentially leading to session hijacking.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-h8gp-q3m8-2gvr

## What is CVE-2026-92839?

CVE-2026-92839 is a medium-severity cross-site scripting vulnerability in Canva, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Canva Desktop before v1.125.0 performed double decoding in the deeplink handler. A threat actor could cause the application to load arbitrary same-origin content under the user’s session.

Weakness: CWE-174 (Double Decoding of the Same Data)

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


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

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

## Is CVE-2026-92839 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92839 is a medium-severity cross-site scripting vulnerability in Canva, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92839 in the wild and no public exploit code.

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

## Sources

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

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