CVE-2026-49740

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% 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: epss, secondary
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

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

TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry database table) could inject a crafted serialized payload to trigger PHP Object Injection, potentially exploiting a gadget chain to achieve Remote Code Execution or other high-impact effects. Exploiting this vulnerability requires direct local write access to the storage, such as the SQL database or file system. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, 13.0.0-13.4.31 and 14.0.0-14.3.3.

CVSS v3
6.3
EG Score
6.3(medium)
EPSS
11.9%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 9, 2026

Advisory Details (3)

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

TYPO3-CORE-SA-2026-018: Insecure Deserialization in Core API - TYPO3 News

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

commit 87cd7c5b710c (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 87cd7c5b710c — awaiting tagged release

https://github.com/TYPO3/typo3/commit/87cd7c5b710c44d3606fed277b040a75dc6a9c02
github_commit

commit 48bcf24f31f5 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 48bcf24f31f5 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/48bcf24f31f52cc0b43d3bea4984634bd2cf85c7

Vendor Advisories for CVE-2026-49740(1)

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

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 65× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 15:47 UTCEG score recompute
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 14:21 UTCEG score recompute
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-03 01:39 UTCEG score recompute
  8. 2026-07-02 01:15 UTCEG score recompute
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-07-01 00:58 UTCEG score recompute
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 00:40 UTCEG score recompute
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 00:23 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 00:06 UTCEG score recompute
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 23:48 UTCEG score recompute
  22. 2026-06-25 23:28 UTCEG score recompute
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 23:10 UTCEG score recompute
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 40 more
  1. 2026-06-23 22:53 UTCEG score recompute
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-22 22:30 UTCEG score recompute
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-21 19:35 UTCEG score recompute
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 01:59 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-20 14:48 UTCEG score recompute
  13. 2026-06-19 19:26 UTCEPSS rescore
  14. 2026-06-19 19:26 UTCEPSS rescore
  15. 2026-06-19 14:19 UTCEG score recompute
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 13:59 UTCEG score recompute
  19. 2026-06-17 17:53 UTCEPSS rescore
  20. 2026-06-17 13:41 UTCEG score recompute
  21. 2026-06-16 17:53 UTCEPSS rescore
  22. 2026-06-16 13:23 UTCEG score recompute
  23. 2026-06-15 17:49 UTCEPSS rescore
  24. 2026-06-15 17:49 UTCEPSS rescore
  25. 2026-06-15 13:05 UTCEG score recompute
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-14 12:47 UTCEG score recompute
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 12:30 UTCEG score recompute
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 12:12 UTCEG score recompute
  33. 2026-06-11 14:00 UTCEPSS rescore
  34. 2026-06-11 11:54 UTCEG score recompute
  35. 2026-06-10 22:19 UTCEPSS rescore
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-10 13:22 UTCEPSS rescore
  38. 2026-06-10 11:37 UTCEG score recompute
  39. 2026-06-09 11:20 UTCEG score recompute
  40. 2026-06-09 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49740?
CVE-2026-49740 is a medium vulnerability published on June 9, 2026. TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry database table) could inject a crafted…
When was CVE-2026-49740 disclosed?
CVE-2026-49740 was first published in the National Vulnerability Database on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49740 actively exploited?
CVE-2026-49740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49740?
CVE-2026-49740 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-49740?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49740, 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-49740

Explore →

Is Your Infrastructure Affected by CVE-2026-49740?

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

Start Free Scan →Browse All CVEs