# CVE-2026-96393: Null dereference in affinity

> Crafted Affinity document files cause an out-of-bounds pointer dereference, leading to application crashes in Affinity by Canva.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-6qg5-7mgr-9fq7

## What is CVE-2026-96393?

CVE-2026-96393 is a low-severity vulnerability in canva affinity, published on 9 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Affinity by Canva app before 3.3.1 (October 2026 release) did not perform adequate bounds checking when parsing Affinity document files, leading to an out-of-bounds pointer dereference. A threat actor could craft an Affinity document that, when opened by a user in Affinity, could result in an application crash.

Weakness: CWE-822 (Untrusted Pointer Dereference)

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


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

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

## Is CVE-2026-96393 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96393 is a low-severity vulnerability in canva affinity, published on 9 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-96393 in the wild and no public exploit code.

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

## Sources

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

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