# CVE-2026-112198: Improper Restriction of XML External Entity Reference in Tactis' NoviGest Desktop App


- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-4cvm-388f-wj2m

## What is CVE-2026-112198?

CVE-2026-112198 is a high-severity vulnerability in Tactis NoviGest Desktop App, published on 28 Oct 2026. 

### Official description

XML External Entity (XXE) injection vulnerability in the SAFT import feature of the NoviGest Desktop App. The application processes user-controlled XML files using a JAXB Unmarshaller without properly disabling external entity resolution. An attacker with access to this functionality could provide a manipulated XML file to read local files accessible to the application process. If the application runs with elevated privileges, sensitive system files could be exposed.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2026-112198 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112198 is a high-severity vulnerability in Tactis NoviGest Desktop App, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112198 in the wild and no public exploit code.

Affected product: Tactis NoviGest Desktop App. 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-112198/ (Markdown: https://insights.sbomify.com/CVE-2026-112198/index.md)
```

## Sources

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

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