# CVE-2026-71518: Typemill < 2.26.0 Authorization Bypass via Media File Download Route

> Unauthenticated attackers can bypass authorization checks in Typemill to download restricted media files using path manipulation techniques.

- **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:** Yes
- **Published:** 17 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-rw94-73mp-v8hw

## What is CVE-2026-71518?

CVE-2026-71518 is a high-severity authentication bypass vulnerability in typemill, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Typemill before 2.26.0 contains an authorization bypass vulnerability in the media file download route that allows unauthenticated attackers to access restricted files by submitting path-equivalent URL variants. Attackers can substitute normalized path forms such as dot-slash prefixes, double slashes, or percent-encoded sequences to pass role-based restriction checks while the filesystem resolves the request to the protected file, enabling unauthorized file download without credentials.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-71518 being exploited?

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

Public exploit code:

- CVE-2026-71518 — Typemill <2.26.0 unauthenticated authorization bypass in media file download (path-equivalent URL variants). Advisory + PoC. (github_poc): https://github.com/IlhomjonR/CVE-2026-71518

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71518 is a high-severity authentication bypass vulnerability in typemill, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71518 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-71518/ (Markdown: https://insights.sbomify.com/CVE-2026-71518/index.md)
```

## Sources

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

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