# CVE-2026-34607: Emlog: Path Traversal in emUnZip() allows arbitrary file write leading to RCE

> An authenticated admin can exploit a path traversal in Emlog's ZIP extraction to write arbitrary files, achieving remote code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-2jg8-rmhm-xv9m

## What is CVE-2026-34607?

CVE-2026-34607 is a high-severity path traversal vulnerability in Emlog Emlog, published on 3 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Emlog is an open source website building system. In versions 2.6.2 and prior, a path traversal vulnerability exists in the emUnZip() function (include/lib/common.php:793). When extracting ZIP archives (plugin/template uploads, backup imports), the function calls $zip->extractTo($path) without sanitizing ZIP entry names. An authenticated admin can upload a crafted ZIP containing entries with ../ sequences to write arbitrary files to the server filesystem, including PHP webshells, achieving Remote Code Execution (RCE). At time of publication, there are no publicly available patches.

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

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

It affects 1 product.


Products: Emlog Emlog.

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

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

## Is CVE-2026-34607 being exploited?

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

## Other vulnerabilities in Emlog Emlog

- [CVE-2025-29401](https://insights.sbomify.com/CVE-2025-29401/): File upload in n/a (critical 9.8)
- [CVE-2025-25783](https://insights.sbomify.com/CVE-2025-25783/): File upload in n/a (critical 9.8)
- [CVE-2023-44973](https://insights.sbomify.com/CVE-2023-44973/): File upload in n/a (critical 9.8)
- [CVE-2023-44974](https://insights.sbomify.com/CVE-2023-44974/): File upload in n/a (critical 9.8)
- [CVE-2023-43291](https://insights.sbomify.com/CVE-2023-43291/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34607 is a high-severity path traversal vulnerability in Emlog Emlog, published on 3 Apr 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-34607 exists.

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

## Sources

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

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