GitHub Advisoryadvisory · Packagist

GHSA-jf56-v8jc-jcc5 TYPO3 CMS has Broken Access Control in its File Abstraction Layer

LOW Published 2026-06-12 Modified 2026-06-12 Official page ↗
Aliases
CVE-2026-49738
Ecosystem
Packagist
Packages
typo3/cms-core
Severity
Low
CVSS vector
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
Weaknesses
CWE-22
Reviewed
2026-06-12

Affected packages

• Packagist typo3/cms-core: < 10.4.57 → fixed in 10.4.57 • Packagist typo3/cms-core: >= 11.0.0, < 11.5.51 → fixed in 11.5.51 • Packagist typo3/cms-core: >= 12.0.0, < 12.4.46 → fixed in 12.4.46 • Packagist typo3/cms-core: >= 13.0.0, < 13.4.31 → fixed in 13.4.31 • Packagist typo3/cms-core: >= 14.0.0, < 14.3.3 → fixed in 14.3.3

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

Related

Alias · CVE (1)

  • CVE-2026-49738 The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory… vulnerability

Weakness · CWE (1)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness

References