# CVE-2026-123989: ESEngine DeepSeek-Reasonix Build Script Execution build.rs loadGitStatus permission


- **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:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-6qf8-c4r6-q4qq, GHSA-vcfm-54ff-823x

## What is CVE-2026-123989?

CVE-2026-123989 is a medium-severity vulnerability in ESEngine DeepSeek-Reasonix, published on 7 Nov 2026. 

### Official description

A vulnerability was found in ESEngine DeepSeek-Reasonix up to 1.33.0. Impacted is the function loadGitStatus of the file build.rs of the component Build Script Execution. Performing a manipulation results in permission issues. The attack may be initiated remotely. Upgrading to version 1.34.0 is recommended to address this issue. The patch is named a54659c2c5b0f4e57aae2b44d41f421c6a71e8cf. You should upgrade the affected component.

Weakness: CWE-275, CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-123989 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123989 is a medium-severity vulnerability in ESEngine DeepSeek-Reasonix, published on 7 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123989 in the wild and no public exploit code.

Affected product: ESEngine DeepSeek-Reasonix. 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-123989/ (Markdown: https://insights.sbomify.com/CVE-2026-123989/index.md)
```

## Sources

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

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