# CVE-2026-49738: TYPO3 CMS - Broken Access Control in File Abstraction Layer > Administrators can bypass path restrictions to access files outside the project root due to flawed prefix checking in TYPO3 CMS. - **Severity:** Low 2.1 (`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`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Jun 2026 - **Updated:** 15 Jul 2026 - **Also known as:** GHSA-jf56-v8jc-jcc5 ## What is CVE-2026-49738? CVE-2026-49738 is a low-severity path traversal vulnerability in TYPO3 CMS, published on 9 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description 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. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-49738? 10 open source packages ship an affected version, including typo3/cms-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms-core` | Packagist | All versions | 10.4.57 | | `typo3/cms-core` | Packagist | All versions | 10.4.57 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.51 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.51 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.46 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.46 | | `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.31 | | `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.31 | | `typo3/cms-core` | Packagist | From 14.0.0 | 14.3.3 | | `typo3/cms-core` | Packagist | From 14.0.0 | 14.3.3 | ## How do I fix CVE-2026-49738? Upgrade typo3/cms-core to a fixed version for your release line: 10.4.57, 11.5.51, 12.4.46 or 13.4.31. ## Is CVE-2026-49738 being exploited? There is no known exploitation of CVE-2026-49738 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-49738 and fix it if it is affected. What it is: CVE-2026-49738 is a low-severity path traversal vulnerability in TYPO3 CMS, published on 9 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-49738 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/cms-core (Packagist): affected all versions; fixed in 10.4.57 - typo3/cms-core (Packagist): affected all versions; fixed in 10.4.57 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.51 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.51 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.46 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.46 - typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.31 - typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.31 - typo3/cms-core (Packagist): affected from 14.0.0; fixed in 14.3.3 - typo3/cms-core (Packagist): affected from 14.0.0; fixed in 14.3.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-49738/ (Markdown: https://insights.sbomify.com/CVE-2026-49738/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49738 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49738 - OSV: https://osv.dev/vulnerability/CVE-2026-49738 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-49738/ Summaries are generated and may contain mistakes; the official description above is the record.