Skip to content
Noroxi
NVD / CVE Program· CNA TYPO3

CVE-2026-0859: TYPO3 CMS Allows Insecure Deserialization via Mailer File Spool

Noroxi assessment

Priority: Monitor (action score 20/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: TYPO3 TYPO3 CMS 10.4.55, 11.5.49, 12.4.41.

Low priority for now. Upgrade to TYPO3 TYPO3 CMS 10.4.55, 11.5.49, 12.4.41 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.2 · v4.0—No exploit Fix available
Published
Jan 13, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · TYPO3
5.2
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-0859

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for typo3 records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
typo3typo3

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • typo3 typo310.0.0 and later · before 10.4.55
  • typo3 typo311.0.0 and later · before 11.5.49
  • typo3 typo312.0.0 and later · before 12.4.41
  • typo3 typo313.0.0 and later · before 13.4.23
  • typo3 typo314.0.0 and later · before 14.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (TYPO3). Independent of NVD's CPE analysis and usually ahead of it.

  • TYPO3 TYPO3 CMS

    • 10.0.0 and later · before 10.4.55affected · semver
    • 11.0.0 and later · before 11.5.49affected · semver
    • 12.0.0 and later · before 12.4.41affected · semver
    • 13.0.0 and later · before 13.4.23affected · semver
    • 14.0.0 and later · before 14.0.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagisttypo3/cms-corefrom 10.0.0 · before 10.4.5510.4.55
Packagisttypo3/cms-corefrom 11.0.0 · before 11.5.4911.5.49
Packagisttypo3/cms-corefrom 12.0.0 · before 12.4.4112.4.41
Packagisttypo3/cms-corefrom 13.0.0 · before 13.4.2313.4.23
Packagisttypo3/cms-corefrom 14.0.0 · before 14.0.214.0.2

Same product

typo3: all records

Other highest-scoring records for the same primary product.

  • CVE-2009-0255The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key with
    60This week
  • CVE-2013-6288Unspecified vulnerability in the Apache Solr for TYPO3 (solr) extension before 2.8.3 for TYPO3 has unknown impact and remote attack vectors,
    41Plan
  • CVE-2013-5303Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors, rela
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-59021Jan 13, 2026 · TYPO3 CMS Allows Broken Access Control in Redirects Module
    21Monitor
  • ← EarlierCVE-2025-59022Jan 13, 2026 · TYPO3 CMS Allows Broken Access Control in Recycler Module
    28Monitor
  • Later →CVE-2026-6553Apr 21, 2026 · TYPO3 CMS Stores Cleartext Password in User Settings Module
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
TYPO3 TYPO3 CMS10.4.55Vendor (CNA)
TYPO3 TYPO3 CMS11.5.49Vendor (CNA)
TYPO3 TYPO3 CMS12.4.41Vendor (CNA)
TYPO3 TYPO3 CMS13.4.23Vendor (CNA)
TYPO3 TYPO3 CMS14.0.2Vendor (CNA)
Packagist:typo3/cms-core10.4.55Package registry (OSV)
Packagist:typo3/cms-core11.5.49Package registry (OSV)
Packagist:typo3/cms-core12.4.41Package registry (OSV)
Packagist:typo3/cms-core13.4.23Package registry (OSV)
Packagist:typo3/cms-core14.0.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python
payload = sock.recv(65536)job = pickle.loads(payload)

Fixed

python
payload = sock.recv(65536)if not hmac.compare_digest(sign(payload), header_sig):    raise PermissionError("invalid signature")job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records