Vulnerability advisory

GHSA-jf56-v8jc-jcc5

TYPO3 CMS has Broken Access Control in its File Abstraction Layer

Published Jun 12, 2026Updated Sep 10, 2026OSV record ↗

Also known as CVE-2026-49738

Severity

CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Affected versions

typo3/cms-core Packagist

All typo3/cms-core advisories →

Affected	Fixed in
All versions before 10.4.57	`10.4.57`Advisories →
Also listed as affected (110) `v10.0.0` `v10.1.0` `v10.2.0` `v10.2.1` `v10.2.2` `v10.3.0` `v10.4.0` `v10.4.1` `v10.4.10` `v10.4.11` `v10.4.12` `v10.4.13` `v10.4.14` `v10.4.15` `v10.4.16` `v10.4.17` `v10.4.18` `v10.4.19` `v10.4.2` `v10.4.20` `v10.4.21` `v10.4.22` `v10.4.23` `v10.4.24` `v10.4.25` `v10.4.26` `v10.4.27` `v10.4.28` `v10.4.29` `v10.4.3` `v10.4.30` `v10.4.31` `v10.4.32` `v10.4.33` `v10.4.34` `v10.4.36` `v10.4.37` `v10.4.4` `v10.4.5` `v10.4.6` `v10.4.7` `v10.4.8` `v10.4.9` `v8.7.10` `v8.7.11` `v8.7.12` `v8.7.13` `v8.7.14` `v8.7.15` `v8.7.16` `v8.7.17` `v8.7.18` `v8.7.19` `v8.7.20` `v8.7.21` `v8.7.22` `v8.7.23` `v8.7.24` `v8.7.25` `v8.7.26` `v8.7.27` `v8.7.28` `v8.7.29` `v8.7.30` `v8.7.31` `v8.7.32` `v8.7.7` `v8.7.8` `v8.7.9` `v9.0.0` `v9.1.0` `v9.2.0` `v9.2.1` `v9.3.0` `v9.3.1` `v9.3.2` `v9.3.3` `v9.4.0` `v9.5.0` `v9.5.1` `v9.5.10` `v9.5.11` `v9.5.12` `v9.5.13` `v9.5.14` `v9.5.15` `v9.5.16` `v9.5.17` `v9.5.18` `v9.5.19` `v9.5.2` `v9.5.20` `v9.5.21` `v9.5.22` `v9.5.23` `v9.5.24` `v9.5.25` `v9.5.26` `v9.5.27` `v9.5.28` `v9.5.29` `v9.5.3` `v9.5.30` `v9.5.31` `v9.5.4` `v9.5.5` `v9.5.6` `v9.5.7` `v9.5.8` `v9.5.9`
`11.0.0` to before 11.5.51	`11.5.51`Advisories →
Also listed as affected (51) `v11.0.0` `v11.1.0` `v11.1.1` `v11.2.0` `v11.3.0` `v11.3.1` `v11.3.2` `v11.3.3` `v11.4.0` `v11.5.0` `v11.5.1` `v11.5.10` `v11.5.11` `v11.5.12` `v11.5.13` `v11.5.14` `v11.5.15` `v11.5.16` `v11.5.17` `v11.5.18` `v11.5.19` `v11.5.2` `v11.5.20` `v11.5.21` `v11.5.22` `v11.5.23` `v11.5.24` `v11.5.25` `v11.5.26` `v11.5.27` `v11.5.28` `v11.5.29` `v11.5.3` `v11.5.30` `v11.5.31` `v11.5.32` `v11.5.33` `v11.5.34` `v11.5.35` `v11.5.36` `v11.5.37` `v11.5.38` `v11.5.39` `v11.5.4` `v11.5.40` `v11.5.41` `v11.5.5` `v11.5.6` `v11.5.7` `v11.5.8` `v11.5.9`
`12.0.0` to before 12.4.46	`12.4.46`Advisories →
Also listed as affected (53) `v12.0.0` `v12.1.0` `v12.1.1` `v12.1.2` `v12.1.3` `v12.2.0` `v12.3.0` `v12.4.0` `v12.4.1` `v12.4.10` `v12.4.11` `v12.4.12` `v12.4.13` `v12.4.14` `v12.4.15` `v12.4.16` `v12.4.17` `v12.4.18` `v12.4.19` `v12.4.2` `v12.4.20` `v12.4.21` `v12.4.22` `v12.4.23` `v12.4.24` `v12.4.25` `v12.4.26` `v12.4.27` `v12.4.28` `v12.4.29` `v12.4.3` `v12.4.30` `v12.4.31` `v12.4.32` `v12.4.33` `v12.4.34` `v12.4.35` `v12.4.36` `v12.4.37` `v12.4.38` `v12.4.39` `v12.4.4` `v12.4.40` `v12.4.41` `v12.4.42` `v12.4.43` `v12.4.44` `v12.4.45` `v12.4.5` `v12.4.6` `v12.4.7` `v12.4.8` `v12.4.9`
`13.0.0` to before 13.4.31	`13.4.31`Advisories →
Also listed as affected (39) `v13.0.0` `v13.0.1` `v13.1.0` `v13.1.1` `v13.2.0` `v13.2.1` `v13.3.0` `v13.3.1` `v13.4.0` `v13.4.1` `v13.4.10` `v13.4.11` `v13.4.12` `v13.4.13` `v13.4.14` `v13.4.15` `v13.4.16` `v13.4.17` `v13.4.18` `v13.4.19` `v13.4.2` `v13.4.20` `v13.4.21` `v13.4.22` `v13.4.23` `v13.4.24` `v13.4.25` `v13.4.26` `v13.4.27` `v13.4.28` `v13.4.29` `v13.4.3` `v13.4.30` `v13.4.4` `v13.4.5` `v13.4.6` `v13.4.7` `v13.4.8` `v13.4.9`
`14.0.0` to before 14.3.3	`14.3.3`Advisories →
Also listed as affected (9) `v14.0.0` `v14.0.1` `v14.0.2` `v14.1.0` `v14.1.1` `v14.2.0` `v14.3.0` `v14.3.1` `v14.3.2`

Description

Problem

The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.

Solution

Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits

TYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.

Resources

TYPO3-CORE-SA-2026-016