# CVE-2026-15326: halo-dev halo Theme Installation ThemeUtils.java ThemeUtils.unzipThemeTo path traversal

> Remote attackers can exploit path traversal in Halo CMS theme installation to read or modify arbitrary files on the server.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-9p22-639x-ghp4

## What is CVE-2026-15326?

CVE-2026-15326 is a medium-severity path traversal vulnerability in halo-dev halo, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was identified in halo-dev halo up to 2.24.2. This affects the function ThemeUtils.unzipThemeTo of the file ThemeUtils.java of the component Theme Installation. Such manipulation of the argument metadata.name leads to path traversal. The attack may be launched remotely. The exploit is publicly available and might be used. The project closed the issue as "duplicate" but did not reference any other issue, report, or CVE.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-15326 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15326 is a medium-severity path traversal vulnerability in halo-dev halo, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15326 exists.

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

## Sources

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

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