# CVE-2026-45729: ThorVG: Null pointer dereference in SVG loader causes crash via 6-byte malformed input

> An attacker can crash applications using ThorVG by providing a small malformed SVG file, causing a null pointer dereference.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **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:** Yes
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-45729, GHSA-f863-8ghq-7h64, UBUNTU-CVE-2026-45729

## What is CVE-2026-45729?

CVE-2026-45729 is a medium-severity vulnerability in thorvg, published on 1 Jun 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

Thor Vector Graphics (ThorVG) is a production-ready vector graphics engine. Prior to version 1.0.5, a null pointer dereference in SvgLoader::run() allows any caller that passes untrusted SVG data to Picture::load() to crash the process with a 6-byte payload. This issue has been patched in version 1.0.5.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Upgrade to a fixed version.

## Is CVE-2026-45729 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45729 exists.

Public exploit code:

- ThorVG NULL pointer dereference via malformed SVG — AFL++ fuzzing writeup (github_poc): https://github.com/yeahhbean/CVE-2026-45729

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45729 is a medium-severity vulnerability in thorvg, published on 1 Jun 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45729 exists.

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

## Sources

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

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