CVE-2026-0859

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% 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, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

TYPO3's mail‑file spool deserialization flaw lets local users with write access to the spool directory craft a malicious file that is deserialized during the mailer:spool:send command, enabling arbitrary PHP code execution on the web server. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

January 13, 2026

Last Modified

June 17, 2026

Advisory Details (4)

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

TYPO3-CORE-SA-2026-004: Insecure Deserialization via Mailer File Spool - TYPO3 News

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

commit e0f0ceee480c (TYPO3/typo3)

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

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

commit 722bf71c118b (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 722bf71c118b — awaiting tagged release

https://github.com/TYPO3/typo3/commit/722bf71c118b0a8e4f2c2494854437d846799a13
github_commit

commit 3225d705080a (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 3225d705080a — awaiting tagged release

https://github.com/TYPO3/typo3/commit/3225d705080a1bde57a66689621c947da5a4782f

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
typo3/cms-corev10.0.0 ... v10.4.9 (43 versions)10.4.55—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 21× 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.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-09-19 04:36 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 05:14 UTCEPSS rescore
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-11 09:36 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-31 08:25 UTCOSV refresh
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-28 21:40 UTCEPSS rescore
  18. 2026-08-27 14:24 UTCEPSS rescore
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-21 23:48 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 75 more
  1. 2026-08-14 14:48 UTCEG score recompute
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 13:50 UTCEPSS rescore
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-10 23:59 UTCEPSS rescore
  6. 2026-08-09 20:26 UTCEG score recompute
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-08 00:58 UTCEG score recompute
  10. 2026-08-06 13:46 UTCEPSS rescore
  11. 2026-08-06 05:58 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-04 15:09 UTCEPSS rescore
  14. 2026-08-04 10:38 UTCEPSS rescore
  15. 2026-08-03 10:35 UTCEPSS rescore
  16. 2026-08-03 00:00 UTCEG score recompute
  17. 2026-08-02 02:26 UTCEPSS rescore
  18. 2026-08-01 04:15 UTCEPSS rescore
  19. 2026-07-30 16:27 UTCEPSS rescore
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-28 15:36 UTCEPSS rescore
  22. 2026-07-27 14:13 UTCEPSS rescore
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-25 14:17 UTCEPSS rescore
  26. 2026-07-24 14:17 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 10:49 UTCOSV refresh
  29. 2026-07-23 03:04 UTCEG score recompute
  30. 2026-07-22 14:08 UTCEPSS rescore
  31. 2026-07-21 15:24 UTCEPSS rescore
  32. 2026-07-20 17:08 UTCEPSS rescore
  33. 2026-07-19 14:30 UTCEPSS rescore
  34. 2026-07-19 02:28 UTCEPSS rescore
  35. 2026-07-16 17:02 UTCEPSS rescore
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-15 02:00 UTCEPSS rescore
  38. 2026-07-13 06:12 UTCEPSS rescore
  39. 2026-07-12 05:46 UTCEPSS rescore
  40. 2026-07-11 08:27 UTCEPSS rescore
  41. 2026-07-09 19:10 UTCEPSS rescore
  42. 2026-07-08 15:15 UTCEPSS rescore
  43. 2026-07-08 15:15 UTCEPSS rescore
  44. 2026-07-07 13:46 UTCEPSS rescore
  45. 2026-07-06 16:27 UTCEPSS rescore
  46. 2026-07-06 06:02 UTCOSV refresh
  47. 2026-07-04 06:31 UTCEPSS rescore
  48. 2026-07-01 15:06 UTCEPSS rescore
  49. 2026-07-01 15:06 UTCEPSS rescore
  50. 2026-06-30 23:22 UTCEPSS rescore
  51. 2026-06-29 14:06 UTCEPSS rescore
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-27 03:08 UTCEPSS rescore
  56. 2026-06-25 13:49 UTCEPSS rescore
  57. 2026-06-24 14:05 UTCEPSS rescore
  58. 2026-06-23 21:32 UTCEPSS rescore
  59. 2026-06-22 14:25 UTCEPSS rescore
  60. 2026-06-22 14:25 UTCEPSS rescore
  61. 2026-06-21 14:56 UTCEPSS rescore
  62. 2026-06-21 14:56 UTCEPSS rescore
  63. 2026-06-21 01:59 UTCEPSS rescore
  64. 2026-06-21 01:59 UTCEPSS rescore
  65. 2026-06-19 19:25 UTCEPSS rescore
  66. 2026-06-18 17:52 UTCEPSS rescore
  67. 2026-06-17 17:53 UTCEPSS rescore
  68. 2026-06-17 17:35 UTCOSV refresh
  69. 2026-06-16 17:52 UTCEPSS rescore
  70. 2026-06-15 17:48 UTCEPSS rescore
  71. 2026-06-14 23:18 UTCEPSS rescore
  72. 2026-06-13 23:00 UTCEPSS rescore
  73. 2026-06-13 23:00 UTCEPSS rescore
  74. 2026-06-12 23:12 UTCEPSS rescore
  75. 2026-06-11 14:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-0859?
CVE-2026-0859 is a high vulnerability published on January 13, 2026. TYPO3's mail‑file spool deserialization flaw lets local users with write access to the spool directory craft a malicious file that is deserialized during the mailer:spool:send command, enabling arbitrary PHP code execution on the web server. This issue affects TYPO3 CMS versions 10.0.0-10.4.54,…
When was CVE-2026-0859 disclosed?
CVE-2026-0859 was first published in the National Vulnerability Database on January 13, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0859 actively exploited?
CVE-2026-0859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.4% of all scored CVEs.
What is the CVSS score of CVE-2026-0859?
CVE-2026-0859 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-0859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0859, 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-0859

Explore →

Is Your Infrastructure Affected by CVE-2026-0859?

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

Start Free Scan →Browse All CVEs