# CVE-2026-79616: Out-of-bounds read vulnerability in Context2D.path and PathSvg.path properties impacts Qt Quick

> An out-of-bounds read in Qt Quick's SVG path parsing allows attackers to cause crashes or leak memory via untrusted SVG strings.

- **Severity:** Low 0.6 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/R:U/RE:L/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** AZL-106830, DEBIAN-CVE-2026-79616, GHSA-mfr5-m9x8-wvjw, UBUNTU-CVE-2026-79616

## What is CVE-2026-79616?

CVE-2026-79616 is a low-severity memory corruption vulnerability in qt, published on 23 Sep 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

Out-of-bounds read while parsing untrusted SVG path strings in Qt Quick's Context2D.path / PathSvg.path.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-79616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79616 is a low-severity memory corruption vulnerability in qt, published on 23 Sep 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-79616 in the wild and no public exploit code.

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

## Sources

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

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