# CVE-2026-38446: Cross-site scripting in n/a

> Attackers can inject malicious JavaScript via ticket titles in osTicket, potentially compromising staff accounts and executing code in their browsers.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-w47h-2qx7-7rfr

## What is CVE-2026-38446?

CVE-2026-38446 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting (XSS) vulnerability exists in osTicket 1.18.3 due to improper sanitization of the thread entry title field. User-controlled input in the title is stored without adequate HTML escaping and later rendered in multiple staff-facing templates without proper output encoding. An attacker can inject arbitrary JavaScript by submitting a crafted ticket reply or email with a malicious subject line.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-38446 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38446 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-38446 in the wild and no public exploit code.

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

## Sources

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

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