# CVE-2026-124557: A vulnerability was detected in OtterMind Chat2DB up to 5.3.8.


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:** 9 Nov 2026
- **Also known as:** GHSA-hp52-9xmj-3539

## What is CVE-2026-124557?

CVE-2026-124557 is a medium-severity vulnerability in OtterMind Chat2DB, published on 9 Nov 2026. 

### Official description

A vulnerability was detected in OtterMind Chat2DB up to 5.3.8. Impacted is the function DbMybatisGenerateServiceImpl.generateClass of the file DbMybatisGenerateServiceImpl.java of the component Class Generator. The manipulation of the argument tableName results in path traversal. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-124557 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124557 is a medium-severity vulnerability in OtterMind Chat2DB, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124557 in the wild and no public exploit code.

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

## Sources

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

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