# CVE-2026-123653: esengine DeepSeek-Reasonix doc.go discoverDocs llm prompting input


- **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:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-46pp-w572-hw78, GHSA-7v48-x992-r5w7

## What is CVE-2026-123653?

CVE-2026-123653 is a medium-severity vulnerability in esengine DeepSeek-Reasonix, published on 6 Nov 2026. 

### Official description

A security vulnerability has been detected in esengine DeepSeek-Reasonix up to 2.52.0. Affected is the function discoverDocs of the file internal/memory/doc.go. The manipulation leads to improper neutralization of input used for llm prompting. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 2.53.0 is able to address this issue. The identifier of the patch is 4ca33493a673c2788aa8598fbca2b2f47a69e1b8. It is suggested to upgrade the affected component.

Weakness: CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data), CWE-1427 (Improper Neutralization of Input Used for LLM Prompting)

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


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

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

## Is CVE-2026-123653 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123653 is a medium-severity vulnerability in esengine DeepSeek-Reasonix, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123653 exists.

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-123653/ (Markdown: https://insights.sbomify.com/CVE-2026-123653/index.md)
```

## Sources

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

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