CVE-2026-5659
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in pytries datrie up to 0.8.3. The affected element is the function Trie.load/Trie.read/Trie.__setstate__ of the file src/datrie.pyx of the component trie File Handler. The manipulation results in deserialization. The attack can be launched remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA deserialization vulnerability exists in pytries datrie up to 0.8.3 within the Trie.load/Trie.read/Trie.__setstate__ functions in src/datrie.pyx. These functions likely use Python's pickle module to deserialize trie file data without proper validation, allowing remote attackers to craft malicious serialized data that could execute arbitrary code during the deserialization process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if datrie library is installedRun 'pip show datrie' or 'pip list | grep -i datrie' to check if the pytries/datrie package is present in the environmentAffected if The datrie package is installed and its version is 0.8.3 or lower
-
Determine the installed datrie versionRun 'pip show datrie' and note the Version field, or import datrie and run 'import datrie; print(datrie.__version__)'Affected if The installed version is 0.8.3 or any version up to and including 0.8.3 (no patch version specified)
-
Locate usage of Trie.load or Trie.read methodsSearch source code files for patterns like 'Trie.load(', 'Trie.read(', or 'trie.load(' to identify where deserialization occursAffected if Code calls Trie.load() or Trie.read() to deserialize trie data from files or network sources
-
Check if loaded data comes from untrusted sourcesAudit the data source for Trie.load/Trie.read calls: verify if input files are user-provided, downloaded from the internet, received over network, or stored in locations with weak access controlsAffected if Trie.load or Trie.read processes data from untrusted or user-controlled sources such as uploads, external APIs, or world-writable files
You are affected if datrie version 0.8.3 or earlier is installed AND your application uses Trie.load(), Trie.read(), or __setstate__ to deserialize trie data from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace unsafe pickle-based deserialization with safer alternatives such as JSON or MessagePack, implement strict input validation on loaded file data, or restrict the load function to trusted sources only. If patch availability is uncertain, consider forking the repository to implement secure deserialization.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5659 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data