# CVE-2026-49738: TYPO3 CMS path traversal in GeneralUtility::isAllowedAbsPath

Source: https://junglewise.ai/threats/cve-2026-49738-typo3-cms-path-traversal-in-generalutility-isallowedabspath  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-09. Updated: 2026-06-12  
License: CC BY 4.0 with a link back

CVE-2026-49738 · Severity: medium · CVSS 4 · Published 2026-06-09

TYPO3 CMS, a popular content management system, contains a flaw in how it validates file paths. This allows administrative users to bypass security restrictions and access or create files in directories outside of the intended project folder. While this requires high-level access to exploit, it could lead to unauthorized access to sensitive system files or configuration data.

Technologies: [typo3/cms-core (Packagist)](https://junglewise.ai/threats/technologies/typo3-cms-core), [Typo3 Cms-Core](https://junglewise.ai/threats/technologies/cms-core). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist), [Typo3](https://junglewise.ai/threats/vendors/typo3).

## Quick answers

**Is CVE-2026-49738 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-49738 being exploited in the wild.

**How severe is CVE-2026-49738?** Medium severity, with a CVSS score of 4, published 9 June 2026.

**Which products and versions are affected?** typo3/cms-core (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57; Typo3 Cms-Core < 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30, 14.0.0-14.3.2.

**Is there a fix for CVE-2026-49738?** Yes. typo3/cms-core (Packagist): upgrade to 10.4.57 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-49738 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-49738?** Check whether you run typo3/cms-core (Packagist) or Typo3 Cms-Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- typo3/cms-core (Packagist): upgrade to 10.4.57 or later

  ```sh
  composer require typo3/cms-core:^10.4.57
  ```


## Technical details

A path traversal vulnerability exists in the TYPO3 File Abstraction Layer (FAL) due to a flawed path allowance check in 'GeneralUtility::isAllowedAbsPath()'. The function performed a plain string prefix comparison without verifying directory separator boundaries (e.g., treating '/var/www/html-other' as a valid subpath of '/var/www/html'). An authenticated administrator with access to FAL can exploit this to create file storage definitions pointing to arbitrary directories outside the project root. This allows for unauthorized read/write access to sensitive files on the underlying filesystem. The issue is resolved in versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, and 14.3.3 LTS.

## Affected products

- TYPO3 cms-core < 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30, 14.0.0-14.3.2

## Identifiers

- CVE-2026-49738
- GHSA-jf56-v8jc-jcc5

## Timeline

- 2026-06-09: advisory: Initial advisory published by TYPO3
- 2026-06-12: disclosed: GHSA published and reviewed

## References

- [https://github.com/TYPO3/typo3/security/advisories/GHSA-jf56-v8jc-jcc5](https://github.com/TYPO3/typo3/security/advisories/GHSA-jf56-v8jc-jcc5)
- [https://github.com/TYPO3/typo3/commit/150a983a5d687cedcfc33bbe9c335d9a13fd05e5](https://github.com/TYPO3/typo3/commit/150a983a5d687cedcfc33bbe9c335d9a13fd05e5)
- [https://github.com/TYPO3/typo3/commit/44c2fa9807944136218a0842e3051c0a379a002d](https://github.com/TYPO3/typo3/commit/44c2fa9807944136218a0842e3051c0a379a002d)
- [https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49738.yaml](https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49738.yaml)
- [https://typo3.org/security/advisory/typo3-core-sa-2026-016](https://typo3.org/security/advisory/typo3-core-sa-2026-016)

## Related threats

- [The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 became ineffective in TYPO3 v13.0, where TYPO3 CMS started](https://junglewise.ai/threats/cve-2026-19418-typo3-cms-broken-access-control-in-backend-and-install-tool)
- [TYPO3 CMS broken access control in Media Module](https://junglewise.ai/threats/cve-2026-49742-typo3-cms-broken-access-control-in-media-module)
- [TYPO3 CMS broken access control in Form Framework form_definition table](https://junglewise.ai/threats/cve-2026-49741-typo3-cms-broken-access-control-in-form-framework-form-definition)
- [TYPO3 CMS insecure deserialization in VariableFrontend and Registry](https://junglewise.ai/threats/cve-2026-49740-typo3-cms-insecure-deserialization-in-variablefrontend-and)
- [TYPO3 CMS broken access control in Backend API](https://junglewise.ai/threats/cve-2026-47352-typo3-cms-broken-access-control-in-backend-api)
