CVE-2026-125159TYPO3 CMS
NVD
Vulnerability Summary
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.
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.
CVSS v4.0 Base Metrics — Score 8.2 (HIGH)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)None
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Affected & Patched Versions
- TYPO3 CMS >= 14.0.0 and < 14.3.12
- TYPO3 CMS >= 13.0.0 and < 13.4.40
- TYPO3 CMS >= 12.0.0 and < 12.4.52
- TYPO3 CMS >= 11.0.0 and < 11.5.57
- TYPO3 CMS >= 10.0.0 and < 10.4.63
- TYPO3 CMS 14.3.12
- TYPO3 CMS 13.4.40
- TYPO3 CMS 12.4.52
- TYPO3 CMS 11.5.57
- TYPO3 CMS 10.4.63
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run TYPO3 CMS and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 17, 2026Published
- Nov 17, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new TYPO3 CMS CVEsYou are reading CVE-2026-125159. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore TYPO3 CMS CVEs
External References
- Vendor Advisoryhttps://news.typo3.com/security/advisory/typo3-core-sa-2026-028
- Patchhttps://github.com/TYPO3/typo3/commit/d6dd82b3c093ca47cc30b1f0ae257e0c1b231d2f
- Patchhttps://github.com/TYPO3/typo3/commit/8ba8dc3151d386e17eb831cfcbb08a90ceecf140
- Patchhttps://github.com/TYPO3/typo3/commit/c6a5a7e1cf8a94ce92a4dacb415302cb9cf200f7
Data last checked: Nov 17, 2026 12:31 UTC