TYPO3 CMS - Information Disclosure in Image Processing (CVE-2026-125159)
Published Last modified Sources: TYPO3, CVE.org, EUVD, BSI
What is affected, what to do
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/.
Update TYPO3 CMS to version 14.3.12, TYPO3 CMS to version 13.4.40, TYPO3 CMS to version 12.4.52.
- Affected
- TYPO3 CMS
lt 14.0.0..14.3.12 - TYPO3 CMS
lt 13.0.0..13.4.40 - TYPO3 CMS
lt 12.0.0..12.4.52 - TYPO3 CMS
lt 11.0.0..11.5.57 - TYPO3 CMS
lt 10.0.0..10.4.63
- TYPO3 CMS
- Fixed in
- 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
- TYPO3 CMS
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.2
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
8.2
CVSS v4
Severity High on the scale from 0 to 10.
Source: TYPO3, CVE.org, EUVD, BSI
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 71.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.2 Methodology
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.2
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 17 November 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-184, CWE-434
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: typo3_advisory, cvelistv5, ENISA EUVD, NVD (NIST), CVE.org (MITRE), BSI CSAF, BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| TYPO3 | TYPO3 CMS |
|
|
| TYPO3 | Extension LTS |
|
|
Vendors and products
Weakness classes (CWE)
CWE-184Incomplete List of Disallowed Inputs
Base
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
Entry at MITRE CWE-184CWE-434Unrestricted Upload of File with Dangerous Type
Base
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Entry at MITRE CWE-434
References & sources
- news.typo3.comsecurity/advisory/typo3-core-sa-2026-028Vendor advisory, euvd
- github.comGit commit of 14.3 brancheuvd, Patch
- github.comGit commit of main brancheuvd, Patch
- github.comGit commit of 13.4 brancheuvd, Patch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedTYPO3
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/TYPO3/typo3/commit/8ba8dc3151d386e17eb831cfcbb08a90ceecf140Reference added —https://github.com/TYPO3/typo3/commit/c6a5a7e1cf8a94ce92a4dacb415302cb9cf200f7Reference added —https://github.com/TYPO3/typo3/commit/d6dd82b3c093ca47cc30b1f0ae257e0c1b231d2fSource identifier: f4fb688c-4412-4426-b4b8-421ecf27b14a
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-125159","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-17T11:30:16.679922Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedTYPO3
CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weakness type: CWE-184, CWE-434
Description added or changed
Show 6 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.CVSS added —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:XWeakness type (CWE) added —CWE-184Weakness type (CWE) added —CWE-434Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/125xxx/CVE-2026-125159.json">CVE-2026-125159</a>Reference added —https://news.typo3.com/security/advisory/typo3-core-sa-2026-028Source identifier: f4fb688c-4412-4426-b4b8-421ecf27b14a
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-125159"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-125159.svg?lang=en" alt="CVE-2026-125159 – NEOSEC Intel" height="20"></a>