# CVE-2026-116608: DAMO Academy VideoLLaMA2 Model Loading __init__.py load_pretrained_model integrity check


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-98hf-f439-379p

## What is CVE-2026-116608?

CVE-2026-116608 is a medium-severity vulnerability in DAMO Academy VideoLLaMA2, published on 27 Oct 2026. 

### Official description

A security vulnerability has been detected in DAMO Academy VideoLLaMA2 up to 1.1. Affected by this issue is the function load_pretrained_model of the file videollama2/model/__init__.py of the component Model Loading. The manipulation of the argument _name_or_path leads to improper validation of integrity check value. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-354 (Improper Validation of Integrity Check Value), CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-116608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116608 is a medium-severity vulnerability in DAMO Academy VideoLLaMA2, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116608 in the wild and no public exploit code.

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

## Sources

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

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