CVE-2026-124318: Treeio through 2.0 Insecure Deserialization RCE via Admin-Editable Pickle Fields

Published Nov 7, 2026

Updated

Treeio through 2.0 contains an insecure deserialization vulnerability in UpdateRecord.getformatstrings and ModuleSetting.loads that allows staff users to execute code via unverified pickle data. Attackers can store a crafted base64 pickle payload in an UpdateRecord formatstrings field through the Django admin, executing Python code as the web server user when news feeds render.

Event History

Nov 7, 2026

CVE Published

via MITRE·02:17 PM

Data Sourced

via MITRE·02:17 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·03:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

An attacker needs staff-level access to the Django admin so they can place a crafted base64 pickle payload into an UpdateRecord format_strings field.

When does the malicious payload execute, and with what privileges?

The payload executes when news feeds render. The resulting Python code runs as the web server user.

Are installations affected by default?

The available information does not establish whether the vulnerable fields are exposed or usable in a default deployment. Exploitation specifically depends on access to the Django admin and the ability to edit the affected UpdateRecord field.

CVE-2026-124318: Treeio through 2.0 Insecure Deserialization RCE via Admin-Editable Pickle Fields

Event History

Frequently Asked Questions

Who can exploit this issue?

When does the malicious payload execute, and with what privileges?

Are installations affected by default?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

When does the malicious payload execute, and with what privileges?

Are installations affected by default?