UnstructuredApplication
CVE-2025-64712
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 · uneditedThe unstructured library provides open-source components for ingesting and pre-processing images and text documents, such as PDFs, HTML, Word docs, and many more. Prior to version 0.18.18, a path traversal vulnerability in the partition_msg function allows an attacker to write or overwrite arbitrary files on the filesystem when processing malicious MSG files with attachments. This issue has been patched in version 0.18.18.
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 · high confidenceA path traversal vulnerability in the partition_msg function of the unstructured library (versions prior to 0.18.18) allows attackers to write or overwrite arbitrary files on the filesystem when processing malicious MSG file attachments. The critical severity (CVSS 9.8) stems from the ability to write files to arbitrary locations via path traversal sequences in attachment filenames.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
UnstructuredApplication
< 0.18.18CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check if unstructured library is installedRun 'pip show unstructured' or check your requirements.txt/pip freeze for the unstructured packageAffected if The package is installed and the version is less than 0.18.18
-
Verify the installed version numberCompare the output from pip show against the affected version range: versions prior to 0.18.18Affected if The installed version is 0.18.17 or lower, or the version cannot be determined (older install without version pinning)
-
Identify usage of the partition_msg functionSearch your codebase for calls to 'partition_msg' function from the unstructured library, or check logs/process traces for this function being invokedAffected if Your code or workflow calls the partition_msg function to process MSG files
-
Confirm MSG file processing workflowInspect any data pipelines, scripts, or configurations that process .msg email attachment files using the unstructured libraryAffected if Your environment processes MSG files through the vulnerable function
You are affected if the unstructured library version is below 0.18.18 AND your system uses partition_msg to process MSG files 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.
dbcve · scoped0.18.18
Upgrade the unstructured library to version 0.18.18 or later. Until upgraded, avoid processing untrusted MSG files with the affected library versions.
0.18.18
- Check the current version of the unstructured library installed in your environment using 'pip show unstructured' or 'pip list | grep unstructured'
- Upgrade to version 0.18.18 or later by running 'pip install --upgrade unstructured==0.18.18' or 'pip install unstructured>=0.18.18'
- Verify the upgrade was successful by running 'pip show unstructured' and confirming the version number is 0.18.18 or higher
- If using the partition_msg function, test with a benign MSG file to confirm functionality is maintained after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unstructured
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64712 — 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-2025-64712 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