How severe is CVE-2026-49742?

No CVSS score has been assigned to CVE-2026-49742 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-49742?

CVE-2026-49742 affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-filelist (Packagist), typo3/cms-filelist (Packagist), typo3/cms-filelist (Packagist), typo3/cms-filelist (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-49742?

Update typo3/cms-core to 11.5.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49742 is resolved across your whole dependency graph.

How do I detect CVE-2026-49742 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-49742 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-49742 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-49742 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-49742?

CVE-2026-49742 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-49742?

CVE-2026-49742 is classified as Path Traversal (CWE-22), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-49742 published, and has it been updated?

CVE-2026-49742 was published on June 9, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-49742 — typo3/cms-core

Fix: TYPO3/typo3@ad636b6

CVE-2026-49742 is a Path Traversal vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

TYPO3 CMS - Broken Access Control in Media Module

Also known asGHSA-chm7-4vch-h8vr

Published

Jun 9, 2026

Updated

Aug 12, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-49742.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

8 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-filelist🐘typo3/cms-filelist🐘typo3/cms-filelist🐘typo3/cms-filelist

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Problem

Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose sensitive files such as log files.

Solution

Update to TYPO3 versions 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 Hyunseo Shin for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.

Resources

TYPO3-CORE-SA-2026-013

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.51	11.5.51`composer require typo3/cms-core:^11.5.51`
🐘Packagist	`typo3/cms-core`	≥ 12.0.0&&< 12.4.46	12.4.46`composer require typo3/cms-core:^12.4.46`
🐘Packagist	`typo3/cms-core`	≥ 13.0.0&&< 13.4.31	13.4.31`composer require typo3/cms-core:^13.4.31`
🐘Packagist	`typo3/cms-core`	≥ 14.0.0&&< 14.3.3	14.3.3`composer require typo3/cms-core:^14.3.3`
🐘Packagist	`typo3/cms-filelist`	≥ 11.0.0&&< 11.5.51	11.5.51`composer require typo3/cms-filelist:^11.5.51`
🐘Packagist	`typo3/cms-filelist`	≥ 12.0.0&&< 12.4.46	12.4.46`composer require typo3/cms-filelist:^12.4.46`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 11.5.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49742 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Problem Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose sensitive files such as log files. ### Solution Update to TYPO3 versions 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 Hyunseo Shin for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it. ### Resources * [TYPO3-CORE-SA-2026-013]

O3 Security · Impact-Aware SCA

Is CVE-2026-49742 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works