# CVE-2026-116095: smg-project smg llm-multimodal jpeg_turbo.rs decode_jpeg_rgb memory allocation


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-55xq-367r-px8q

## What is CVE-2026-116095?

CVE-2026-116095 is a medium-severity vulnerability in smg-project smg, published on 25 Oct 2026. 

### Official description

A vulnerability was identified in smg-project smg 1.7.0/1.8.0/1.9.0/1.10.0/1.10.1. Affected is the function jpeg_turbo::decode_jpeg_rgb of the file crates/multimodal/src/jpeg_turbo.rs of the component llm-multimodal. The manipulation leads to uncontrolled memory allocation. The attack can be initiated remotely. The exploit is publicly available and might be used. Upgrading to version 1.11.0 is able to address this issue. The identifier of the patch is 8f51b57e219a914089e345b704c3c8de37a3bb8e. It is advisable to upgrade the affected component.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-116095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116095 is a medium-severity vulnerability in smg-project smg, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116095 exists.

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

## Sources

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

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