Advisory record · GHSA-jf56-v8jc-jcc5

TYPO3 CMS has Broken Access Control in its File Abstraction Layer

CVSS 2.1 LowEPSS 0.0036 · 29th percentile

Published by the GitHub Advisory Database at 12 Jun 2026, 19:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist<10.4.57 || >=11.0.0, <11.5.51 || >=12.0.0, <12.4.46 || >=13.0.0, <13.4.31 || >=14.0.0, <14.3.310.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3
Identifiers
GHSA-jf56-v8jc-jcc5 · CVE-2026-49738 · PKSA-gj1k-954p-nhmk
Weakness (CWE)
CWE-22
Published
12 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The typo3/cms-core Packagist package is affected in versions below 10.4.57, from 11.0.0 to below 11.5.51, from 12.0.0 to below 12.4.46, from 13.0.0 to below 13.4.31, and from 14.0.0 to below 14.3.3. A path check in GeneralUtility::isAllowedAbsPath() used a plain string prefix comparison without a directory boundary, so paths such as a sibling directory sharing the project root's prefix were accepted. An administrator with access to the File Abstraction Layer could use this to create file storages pointing outside the project root. Upgrade to 10.4.57, 11.5.51, 12.4.46, 13.4.31, or 14.3.3.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.1 Low 4.0 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 CNA (TYPO3)
  • CISA KEV Not listed.
  • EPSS 0.0036, the 29th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:57 UTC First seen by agentprime
  2. 31 Oct 2026, 13:57 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.