# CVE-2026-124589: lxtGH OMG-Seg MoE Shard Checkpoint Loader handle_moe_load_and_save.py load_state_dict_into_model 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:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-4265-pjrw-m328

## What is CVE-2026-124589?

CVE-2026-124589 is a medium-severity vulnerability in lxtGH OMG-Seg, published on 9 Nov 2026. 

### Official description

A weakness has been identified in lxtGH OMG-Seg up to f3b26b609bae919760cd3ccf09c36179bb8624a0. This affects the function load_state_dict_into_model of the file omg_llava/xtuner/utils/handle_moe_load_and_save.py of the component MoE Shard Checkpoint Loader. Executing a manipulation of the argument weight_map can lead to path traversal. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. 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-124589?


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

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

## Is CVE-2026-124589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124589 is a medium-severity vulnerability in lxtGH OMG-Seg, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124589 exists.

Affected product: lxtGH OMG-Seg. 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-124589/ (Markdown: https://insights.sbomify.com/CVE-2026-124589/index.md)
```

## Sources

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

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