# CVE-2026-122188: DeepGraphLearning KnowledgeGraphEmbedding Checkpoint Loading run.py override_config path traversal


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-2h77-6hv6-rjwj

## What is CVE-2026-122188?

CVE-2026-122188 is a medium-severity vulnerability in DeepGraphLearning KnowledgeGraphEmbedding, published on 5 Nov 2026. 

### Official description

A flaw has been found in DeepGraphLearning KnowledgeGraphEmbedding up to 2e440e0f9c687314d5ff67ead68ce985dc446e3a. Impacted is the function override_config of the file codes/run.py of the component Checkpoint Loading. This manipulation of the argument data_path causes path traversal. The attack can be initiated remotely. The exploit has been published and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. 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-122188?


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

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

## Is CVE-2026-122188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122188 is a medium-severity vulnerability in DeepGraphLearning KnowledgeGraphEmbedding, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122188 exists.

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

## Sources

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

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