GHSA-jf56-v8jc-jcc5

TYPO3 CMS has Broken Access Control in its File Abstraction Layer

At a glance

Published
Updated
CVE
CVE-2026-49738
CVSS_V4
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

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](https://typo3.org/security/advisory/typo3-core-sa-2026-016)

Affected packages

PackageVersions
Packagist · typo3/cms-coreintroduced 0, fixed 10.4.57
Packagist · typo3/cms-coreintroduced 11.0.0, fixed 11.5.51
Packagist · typo3/cms-coreintroduced 12.0.0, fixed 12.4.46
Packagist · typo3/cms-coreintroduced 13.0.0, fixed 13.4.31
Packagist · typo3/cms-coreintroduced 14.0.0, fixed 14.3.3

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database