{"id":"CVE-2026-49738","aliases":["GHSA-jf56-v8jc-jcc5"],"title":"TYPO3 CMS has Broken Access Control in its File Abstraction Layer","summary":"TYPO3 CMS has Broken Access Control in its File Abstraction Layer","severity":"low","cwe":["CWE-22"],"vendor":"typo3","product":"typo3/cms-core","ecosystem":"composer","affected":["typo3/cms-core < 10.4.57","typo3/cms-core >= 11.0.0, < 11.5.51","typo3/cms-core >= 12.0.0, < 12.4.46","typo3/cms-core >= 13.0.0, < 13.4.31","typo3/cms-core >= 14.0.0, < 14.3.3"],"patched":["typo3/cms-core 10.4.57","typo3/cms-core 11.5.51","typo3/cms-core 12.4.46","typo3/cms-core 13.4.31","typo3/cms-core 14.3.3"],"published":"2026-06-12","updated":"2026-06-12","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-jf56-v8jc-jcc5","references":[{"url":"https://github.com/TYPO3/typo3/security/advisories/GHSA-jf56-v8jc-jcc5"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49738"},{"url":"https://github.com/TYPO3/typo3/commit/150a983a5d687cedcfc33bbe9c335d9a13fd05e5"},{"url":"https://github.com/TYPO3/typo3/commit/44c2fa9807944136218a0842e3051c0a379a002d"},{"url":"https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49738.yaml"},{"url":"https://typo3.org/security/advisory/typo3-core-sa-2026-016"},{"url":"https://github.com/advisories/GHSA-jf56-v8jc-jcc5"}],"tags":["ghsa","composer"],"epss":0.00356,"epssPercentile":0.29377,"ingestedAt":"2026-07-07T15:41:59.183Z","slug":"CVE-2026-49738","body":"## Overview\n\n### Problem\nThe 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.\n\n### Solution\nUpdate 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.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* [TYPO3-CORE-SA-2026-016](https://typo3.org/security/advisory/typo3-core-sa-2026-016)\n\n## Affected packages\n\n- `typo3/cms-core < 10.4.57`\n- `typo3/cms-core >= 11.0.0, < 11.5.51`\n- `typo3/cms-core >= 12.0.0, < 12.4.46`\n- `typo3/cms-core >= 13.0.0, < 13.4.31`\n- `typo3/cms-core >= 14.0.0, < 14.3.3`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `typo3/cms-core 10.4.57`\n- `typo3/cms-core 11.5.51`\n- `typo3/cms-core 12.4.46`\n- `typo3/cms-core 13.4.31`\n- `typo3/cms-core 14.3.3`","depth":"sunlit","depthScore":14,"depthScoreParts":{"impact":13.8,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}