CVE-2026-125159 json
TYPO3 CMS - Information Disclosure in Image Processing
published yesterday modified yesterday also EUVD-2026-126976
- cvss
- 8.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
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.
Patch / fix
- TYPO3 TYPO3 CMS 10.4.63, 11.5.57, 12.4.52, 13.4.40, 14.3.12
- github.com/TYPO3/typo3@d6dd82b commit
- github.com/TYPO3/typo3@8ba8dc3 commit
- github.com/TYPO3/typo3@c6a5a7e commit
Is CVE-2026-125159 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | 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 |
| CNA | 4.0 | 8.2 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- TYPO3 TYPO3 CMS
Classification
References
-
github.com
/TYPO3/typo3/commit/d6dd82b3c093ca47cc30b1f0ae257e0c1b231d2f
patch
-
github.com
/TYPO3/typo3/commit/8ba8dc3151d386e17eb831cfcbb08a90ceecf140
patch
-
github.com
/TYPO3/typo3/commit/c6a5a7e1cf8a94ce92a4dacb415302cb9cf200f7
patch
-
news.typo3.com
/security/advisory/typo3-core-sa-2026-028
vendor-advisory
Sources
- CVE List CVE-2026-125159
- NVD CVE-2026-125159
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.