# CVE-2026-110642: xhtml2pdf before 0.2.19 OS Command Injection via startViewer File Name

> Attackers can execute arbitrary OS commands via crafted filenames when using the startViewer feature in xhtml2pdf.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110642, GHSA-p77q-xqj7-2552, UBUNTU-CVE-2026-110642, openSUSE-SU-2026:12160-1

## What is CVE-2026-110642?

CVE-2026-110642 is a high-severity command injection vulnerability in xhtml2pdf, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

xhtml2pdf before 0.2.19 contains an OS command injection vulnerability in pisa.startViewer() that allows attackers to execute commands by interpolating unescaped file names into os.system. Attackers can supply an input file whose name contains a double quote and shell metacharacters, which runs OS commands as the invoking user when the pisa tool is used with -s/--start-viewer.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-xhtml2pdf` | openSUSE:Tumbleweed | All versions | 0.2.24-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-110642 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110642 is a high-severity command injection vulnerability in xhtml2pdf, published on 14 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-110642 in the wild and no public exploit code.

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

## Sources

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

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