# CVE-2026-110666: cemtan sar2html File Upload sar2html.py updateDb path traversal

> Attackers can exploit a path traversal vulnerability in the file upload function to read or modify arbitrary files on the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gr6x-mh72-59hj

## What is CVE-2026-110666?

CVE-2026-110666 is a medium-severity path traversal vulnerability in cemtan sar2html, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in cemtan sar2html 4.0.0. Affected is the function updateDb of the file sar2html.py of the component File Upload. The manipulation leads to path traversal. Remote exploitation of the attack is possible. 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-110666?


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

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

## Is CVE-2026-110666 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110666 is a medium-severity path traversal vulnerability in cemtan sar2html, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110666 exists.

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

## Sources

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

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