CVE-2026-49742

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:typo3, epss
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
EPSS
23.5%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 11, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

TYPO3-CORE-SA-2026-013: Broken Access Control in Media Module - TYPO3 News

https://typo3.org/security/advisory/typo3-core-sa-2026-013
github_commit

commit caa6b444d7ab (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit caa6b444d7ab — awaiting tagged release

https://github.com/TYPO3/typo3/commit/caa6b444d7ab1bdd1eb76a68004c8be73d98e6ae
github_commit

commit ad636b618384 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit ad636b618384 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/ad636b6183843b57c758a1e12174a75093ac93c3

Vendor Advisories for CVE-2026-49742(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
typo3/cms-corev14.0.0 ... v14.3.2 (9 versions)14.3.3
typo3/cms-filelistv14.0.0 ... v14.3.2 (9 versions)14.3.3

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-01 15:07 UTCEPSS rescore
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 33 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-19 19:26 UTCEPSS rescore
  17. 2026-06-19 19:26 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-16 17:53 UTCEPSS rescore
  22. 2026-06-15 17:49 UTCEPSS rescore
  23. 2026-06-15 17:49 UTCEPSS rescore
  24. 2026-06-14 23:18 UTCEPSS rescore
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-11 14:00 UTCEPSS rescore
  29. 2026-06-10 22:19 UTCEPSS rescore
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-09 11:20 UTCEG score recompute
  33. 2026-06-09 11:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-49742?
CVE-2026-49742 is a high vulnerability published on June 9, 2026. 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…
When was CVE-2026-49742 disclosed?
CVE-2026-49742 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49742 actively exploited?
CVE-2026-49742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49742?
CVE-2026-49742 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-49742?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49742, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49742

Explore →

Is Your Infrastructure Affected by CVE-2026-49742?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.