CVE-2026-124318 Treeio through 2.0 Insecure Deserialization RCE via Admin-Editable Pickle Fields
High 8.6
Published
Updated
Check this codebase for CVE-2026-124318 and fix it if it is affected.
What it is: CVE-2026-124318 is a high-severity vulnerability in treeio, published on 7 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-124318 in the wild and no public exploit code.
Affected product: treeio. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-124318/ (Markdown: https://insights.sbomify.com/CVE-2026-124318/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-124318?
CVE-2026-124318 is a high-severity vulnerability in treeio, published on 7 Nov 2026.
Official description
Treeio through 2.0 contains an insecure deserialization vulnerability in UpdateRecord.get_format_strings 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 format_strings field through the Django admin, executing Python code as the web server user when news feeds render.
Weakness: CWE-502
Which versions are affected by CVE-2026-124318?
How do I fix CVE-2026-124318?
No fix has been published for CVE-2026-124318 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-124318 being exploited?
There is no known exploitation of CVE-2026-124318 in the wild and no public exploit code.
Sources
Also known as GHSA-3rqm-3mpx-jvr5.