CVE-2026-49742
Fix: TYPO3/typo3@ad636b6CVE-2026-49742 is a Path Traversal vulnerability in typo3/cms-core. O3 Security confirms whether CVE-2026-49742 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
TYPO3 CMS - Broken Access Control in Media Module
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-filelist🐘typo3/cms-filelist🐘typo3/cms-filelist🐘typo3/cms-filelistReal-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
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. This issue affects TYPO3 CMS versions 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.51 | 11.5.51 |
| 🐘Packagist | typo3/cms-core | ≥ 12.0.0&&< 12.4.46 | 12.4.46 |
| 🐘Packagist | typo3/cms-core | ≥ 13.0.0&&< 13.4.31 | 13.4.31 |
| 🐘Packagist | typo3/cms-core | ≥ 14.0.0&&< 14.3.3 | 14.3.3 |
| 🐘Packagist | typo3/cms-filelist | ≥ 11.0.0&&< 11.5.51 | 11.5.51 |
| 🐘Packagist | typo3/cms-filelist | ≥ 12.0.0&&< 12.4.46 | 12.4.46 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-49742 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-49742. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-49742 in your dependencies?
O3 detects CVE-2026-49742 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.