CVE-2026-49738: Typo3/cms core TYPO3 CMS Has Broken Access Vulnerability

LOW
Advisory Identifier: GHSA-jf56-v8jc-jcc5
Share
CWE-22
Published
Advisory Summary

CVE-2026-49738 is a LOW typo3 cms has broken access vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Typo3/cms core libraries in the Packagist ecosystem. The issue involves typo3 cms has broken access control in its file abstraction layer. Remediation is available by upgrading affected packages to version 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3.

CVE-2026-49738 at a Glance

CVE Identifier CVE-2026-49738
GHSA Identifier GHSA-jf56-v8jc-jcc5
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Typo3/cms core
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-49738

To remediate this vulnerability, upgrade all affected Typo3/cms core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

typo3/cms-core fixed: 10.4.57 
Upgrade typo3/cms-core to 10.4.57
typo3/cms-core fixed: 11.5.51 
Upgrade typo3/cms-core to 11.5.51
typo3/cms-core fixed: 12.4.46 
Upgrade typo3/cms-core to 12.4.46
typo3/cms-core fixed: 13.4.31 
Upgrade typo3/cms-core to 13.4.31
typo3/cms-core fixed: 14.3.3 
Upgrade typo3/cms-core to 14.3.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for typo3/cms-core

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-49738, inspect your project dependencies for Typo3/cms core:

inspect dependencies for typo3/cms-core

Analyze the terminal output to locate any version of Typo3/cms core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 10.4.57), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Typo3/cms core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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)

CVE-2026-49738 Affected Typo3/cms core Versions

5 component(s)
Fixed Versions:
10.4.5711.5.5112.4.4613.4.3114.3.3
Product / Package Ecosystem Affected Versions Fixed Version
typo3/cms-core
 Packagist
< 10.4.57
10.4.57
typo3/cms-core
 Packagist
≥ 11.0.0
< 11.5.51
11.5.51
typo3/cms-core
 Packagist
≥ 12.0.0
< 12.4.46
12.4.46
typo3/cms-core
 Packagist
≥ 13.0.0
< 13.4.31
13.4.31
typo3/cms-core
 Packagist
≥ 14.0.0
< 14.3.3
14.3.3

References

Typo3/cms core Source Repository REPOSITORY
https://github.com/TYPO3/typo3
Typo3/cms core Security Information SECURITY
https://typo3.org/security/advisory/typo3-core-sa-2026-016
GitHub Advisory / Wiki ADVISORY
https://github.com/TYPO3/typo3/security/advisories/GHSA-jf56-v8jc-jcc5
NVD — CVE-2026-49738 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-49738
Security Fix Commit FIX COMMIT
https://github.com/TYPO3/typo3/commit/150a983a5d687cedcfc33bbe9c335d9a13fd05e5
Security Fix Commit FIX COMMIT
https://github.com/TYPO3/typo3/commit/44c2fa9807944136218a0842e3051c0a379a002d
Typo3/cms core Source Repository REPOSITORY
https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49738.yaml

Frequently Asked Questions

What is CVE-2026-49738?
CVE-2026-49738 is a security vulnerability in Typo3/cms core involving TYPO3 CMS has Broken Access Control in its File Abstraction Layer under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Typo3/cms core versions are affected?
Affected versions include releases prior to 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3 across affected packages: typo3/cms-core.
What version fixes CVE-2026-49738?
Upgrading to 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is typo3/cms-core affected?
Yes, typo3/cms-core is affected in releases prior to 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3. Upgrade your dependency to 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3 or later.
What CWE is associated with CVE-2026-49738?
CVE-2026-49738 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Packagist dependencies for CVE-2026-49738?
Run the dependency tree command: 'inspect dependencies for typo3/cms-core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jf56-v8jc-jcc5",
  "modified" : "2026-06-12T19:09:04Z",
  "published" : "2026-06-12T19:09:04Z",
  "aliases" : [ "CVE-2026-49738" ],
  "summary" : "TYPO3 CMS has Broken Access Control in its File Abstraction Layer",
  "details" : "### 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)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "10.4.57"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "11.0.0"
      }, {
        "fixed" : "11.5.51"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "12.0.0"
      }, {
        "fixed" : "12.4.46"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "13.0.0"
      }, {
        "fixed" : "13.4.31"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "typo3/cms-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "14.0.0"
      }, {
        "fixed" : "14.3.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/security/advisories/GHSA-jf56-v8jc-jcc5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-49738"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/150a983a5d687cedcfc33bbe9c335d9a13fd05e5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/TYPO3/typo3/commit/44c2fa9807944136218a0842e3051c0a379a002d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49738.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/TYPO3/typo3"
  }, {
    "type" : "WEB",
    "url" : "https://typo3.org/security/advisory/typo3-core-sa-2026-016"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-12T19:09:04Z",
    "nvd_published_at" : "2026-06-09T11:16:53Z"
  }
}