# CVE-2026-123367: ThorVG: Heap buffer overflow (OOB write) in bundled jpgd JPEG decoder


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123367, GHSA-mw4c-w54x-248r, UBUNTU-CVE-2026-123367

## What is CVE-2026-123367?

CVE-2026-123367 is a high-severity vulnerability in thorvg, published on 9 Nov 2026. 

### Official description

Thor Vector Graphics (ThorVG) is a production-ready vector graphics engine. Prior to 1.1.2, the bundled jpgd JPEG decoder accepts duplicate component selectors in an SOS scan header, causing each duplicate to increase m_blocks_per_mcu without checking the buffers sized from the frame components. A crafted grayscale JPEG can repeat its component in the SOS header, causing decode paths in src/loaders/jpg/tvgJpgd.cpp to write beyond heap buffers sized for one component. The issue is reachable through direct JPEG decoding and through JPEG images embedded in Lottie content, and confirmed impact is memory corruption followed by a process crash. This issue is fixed in version 1.1.2.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-123367 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123367 is a high-severity vulnerability in thorvg, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123367 in the wild and no public exploit code.

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

## Sources

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

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