Is CVE-2026-49742 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49742 being exploited in the wild.

How severe is CVE-2026-49742?

High severity, with a CVSS score of 4, published 9 June 2026.

Which products and versions are affected?

typo3/cms-core (Packagist) ECOSYSTEM:introduced=11.0.0,fixed=11.5.51; typo3/cms-filelist (Packagist) ECOSYSTEM:introduced=11.0.0,fixed=11.5.51.

Is there a fix for CVE-2026-49742?

Yes. typo3/cms-core (Packagist): upgrade to 11.5.51 or later; typo3/cms-filelist (Packagist): upgrade to 11.5.51 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-49742 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-49742?

Check whether you run typo3/cms-core (Packagist) or typo3/cms-filelist (Packagist) 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.

CVE-2026-49742: TYPO3 CMS broken access control in Media Module

CVE-2026-49742 · Severity: high · CVSS 4 · Published 2026-06-09

TYPO3 CMS, a popular enterprise content management system, contains a security flaw in its Media Module. Authenticated users with basic file download permissions can bypass intended restrictions to download sensitive system files, such as server logs, from the server's root directory. This could lead to the exposure of confidential configuration data or system information, potentially aiding further attacks.

Technologies: typo3/cms-core (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-49742 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49742 being exploited in the wild.
How severe is CVE-2026-49742?: High severity, with a CVSS score of 4, published 9 June 2026.
Which products and versions are affected?: typo3/cms-core (Packagist) ECOSYSTEM:introduced=11.0.0,fixed=11.5.51; typo3/cms-filelist (Packagist) ECOSYSTEM:introduced=11.0.0,fixed=11.5.51.
Is there a fix for CVE-2026-49742?: Yes. typo3/cms-core (Packagist): upgrade to 11.5.51 or later; typo3/cms-filelist (Packagist): upgrade to 11.5.51 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49742 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49742?: Check whether you run typo3/cms-core (Packagist) or typo3/cms-filelist (Packagist) 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 11.5.51 or later
```
composer require typo3/cms-core:^11.5.51
```
typo3/cms-filelist (Packagist): upgrade to 11.5.51 or later
```
composer require typo3/cms-filelist:^11.5.51
```

Technical details

A broken access control vulnerability exists in the TYPO3 Media Module's interaction with the File Abstraction Layer (FAL). Backend users with existing file download permissions can exploit the 'fallback storage' mechanism, which incorrectly resolves file paths relative to the server's document root rather than restricted media directories. This allows for a path traversal-style attack where sensitive files, including system logs and configuration files, can be retrieved by an attacker with low-level backend privileges. The issue is resolved in TYPO3 versions 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, and 14.3.3 LTS.

Affected products

TYPO3 TYPO3 CMS 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-49742
GHSA-chm7-4vch-h8vr

Timeline

2026-06-09: disclosed
2026-06-09: patched
2026-06-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.