# CVE-2026-114040: DT42 BerryNet Model Package Metadata dlmodelmgr.py DLModelManager.get_model_meta path traversal


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-q43h-59xm-9r43

## What is CVE-2026-114040?

CVE-2026-114040 is a medium-severity vulnerability in DT42 BerryNet, published on 21 Oct 2026. 

### Official description

A security vulnerability has been detected in DT42 BerryNet up to 3.10.2. The affected element is the function DLModelManager.get_model_meta of the file berrynet/dlmodelmgr.py of the component Model Package Metadata Handler. The manipulation of the argument label leads to path traversal. The attack is possible to be carried out remotely. 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-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-114040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114040 is a medium-severity vulnerability in DT42 BerryNet, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114040 exists.

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

## Sources

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

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