English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

TYPO3 fixes ten vulnerabilities, some allowing remote code execution

France's CERT-FR has flagged multiple vulnerabilities in the TYPO3 CMS that can lead to remote code execution, denial of service or data exposure. Any site running an unpatched TYPO3 10.x to 14.x release is affected.

What to do now Illustration photo (network cables)
CVSS severity7.7High
EPSS probability1 %
ExploitationNot observed
PatchAvailable
Product
TYPO3
Affected versions
TYPO3 10.x < 10.4.63, 11.x < 11.5.57, 12.x < 12.4.52, 13.x < 13.4.40, 14.x < 14.3.12
Fixed in
10.4.63, 11.5.57, 12.4.52, 13.4.40, 14.3.12
CVE
CVE-2026-119621

On 17 November 2026, CERT-FR issued advisory CERTFR-2026-AVI-1553 covering a batch of security flaws in the TYPO3 content management system. The vendor published ten security advisories the same day, tied to ten CVE identifiers ranging from CVE-2026-119621 to CVE-2026-125165.

The impacts listed cover a wide range: remote arbitrary code execution, remote denial of service, data confidentiality breaches, security policy bypass, server-side request forgery (SSRF) and cross-site scripting (XSS). The advisory does not map individual flaws to specific impacts, nor does it say whether exploitation requires prior authentication.

Five release lines are affected: 10.x before 10.4.63, 11.x before 11.5.57, 12.x before 12.4.52, 13.x before 13.4.40 and 14.x before 14.3.12. Those versions contain the fixes, and CERT-FR points administrators to the vendor's GitHub advisories for patch details.

The source does not report any active exploitation. Since TYPO3 sites are usually internet-facing, though, the presence of a remote code execution flaw makes prompt patching advisable.

Action plan

What to do now

  1. Inventory every TYPO3 instance in your organisation and record its exact version.
  2. Upgrade to TYPO3 10.4.63, 11.5.57, 12.4.52, 13.4.40 or 14.3.12 depending on your release line.
  3. Read the ten vendor GHSA advisories for per-flaw details and any exploitation prerequisites.
  4. As general good practice, review web server and TYPO3 backend logs for unusual activity.

Sources