# CVE-2026-22200: osTicket (1.18.x < 1.18.3, 1.17.x < 1.17.7) PDF Export Arbitrary File Read

> Remote attackers can read arbitrary server files via crafted HTML in tickets exported to PDF, exposing sensitive data in default configurations.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-4hcq-q3qf-q453

## What is CVE-2026-22200?

CVE-2026-22200 is a high-severity path traversal vulnerability in Enhancesoft osTicket, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Enhancesoft osTicket versions 1.18.x prior to 1.18.3 and 1.17.x prior to 1.17.7 contain an arbitrary file read vulnerability in the ticket PDF export functionality. A remote attacker can submit a ticket containing crafted rich-text HTML that includes PHP filter expressions which are insufficiently sanitized before being processed by the mPDF PDF generator during export. When the attacker exports the ticket to PDF, the generated PDF can embed the contents of attacker-selected files from the server filesystem as bitmap images, allowing disclosure of sensitive local files in the context of the osTicket application user. This issue is exploitable in default configurations where guests may create tickets and access ticket status, or where self-registration is enabled.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Enhancesoft Osticket.

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

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

## Is CVE-2026-22200 being exploited?

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

Public exploit code:

- CVE-2026-22200: Arbitrary file read + CNEXT RCE in osTicket (github_poc): https://github.com/horizon3ai/CVE-2026-22200
- osTicket Arbitrary File Read via PHP Filter Chains in mPDF (metasploit)
- osTicket - Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-22200.yaml

## Other vulnerabilities in Enhancesoft osTicket

- [CVE-2021-42235](https://insights.sbomify.com/CVE-2021-42235/): SQL injection in n/a (critical 9.8)
- [CVE-2020-24881](https://insights.sbomify.com/CVE-2020-24881/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-31888](https://insights.sbomify.com/CVE-2022-31888/): Other in n/a (high 8.8)
- [CVE-2019-14749](https://insights.sbomify.com/CVE-2019-14749/): Other in n/a (high 8.8)
- [CVE-2018-7195](https://insights.sbomify.com/CVE-2018-7195/): Auth bypass in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22200 is a high-severity path traversal vulnerability in Enhancesoft osTicket, published on 12 Jan 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-22200 exists.

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

## Sources

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

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