# CVE-2026-109162: TYPO3 CMS - Security Misconfiguration in Form Framework

> Attackers can access uploaded files publicly if custom save paths are configured, bypassing intended storage restrictions in TYPO3 CMS.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/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:** No
- **Published:** 13 Oct 2026
- **Updated:** 16 Oct 2026

## What is CVE-2026-109162?

CVE-2026-109162 is a medium-severity vulnerability in TYPO3 CMS, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Forms using FileUpload or ImageUpload elements with a custom saveToFileMount configured stored uploaded files in the default storage folder 1:/user_upload/ instead of the configured destination. This could cause uploaded files to end up in a publicly accessible storage even though a restricted, non-public storage had been configured. Files stored this way are served directly, without the access checks applied to non-public storages. Forms that use the default value for saveToFileMount are not affected. This issue affects TYPO3 CMS versions 14.0.0-14.3.8.

Weakness: CWE-696 (Incorrect Behavior Order), CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2026-109162 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109162 is a medium-severity vulnerability in TYPO3 CMS, published on 13 Oct 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-109162 in the wild and no public exploit code.

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

## Sources

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

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