# CVE-2026-49133: Typemill < 2.24.0 Path Traversal via ControllerApiImage::getPagemedia()

> Authenticated attackers with Author privileges can read arbitrary files outside the content directory via path traversal in the image API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-pvj2-mj22-xxmq

## What is CVE-2026-49133?

CVE-2026-49133 is a high-severity path traversal vulnerability in typemill, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Typemill before 2.24.0 contains a path traversal vulnerability that allows authenticated attackers with Author-level privileges to read arbitrary files outside the content directory by supplying traversal sequences in the path query parameter passed to Storage::getFile() with an empty folder argument. Attackers can bypass traversal-prevention controls in Storage::getFolderPath() to access sensitive files.

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

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


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

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

## Is CVE-2026-49133 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49133 is a high-severity path traversal vulnerability in typemill, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49133 in the wild and no public exploit code.

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

## Sources

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

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