CVE-2024-46455
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 · uneditedunstructured v.0.14.2 and before is vulnerable to XML External Entity (XXE) via the XMLParser.
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 confidenceThe unstructured library versions 0.14.2 and below contain an XML External Entity (XXE) vulnerability in the XMLParser component. This allows attackers to craft malicious XML input that can cause the parser to read local files, perform server-side request forgery (SSRF), or denial of service attacks.
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
- 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 installed unstructured library versionRun `pip show unstructured` or `pip list | grep unstructured` to see the installed version numberAffected if Version is 0.14.2 or lower
-
Identify XMLParser usage in codeSearch your codebase for imports and usage of XMLParser, such as `from unstructured.partition.xml import XMLParser` or instances where XMLParser is instantiatedAffected if XMLParser class is imported or used in your application code
-
Check for XML file processingReview application logs or code that processes .xml files using the unstructured library, looking for partition calls on XML documentsAffected if Your application parses XML files with unstructured
-
Inspect XMLParser configurationLook for any configuration files or code that instantiates XMLParser with custom settings, check for lxml or defusedxml backendsAffected if XMLParser is configured with default settings (external entity resolution enabled by default)
-
Verify external entity resolution is disabledIf using lxml.etree, verify parser configuration does not set resolve_entities=True; check for defusedxml or lxml's XMLParser with resolve_entities=FalseAffected if No explicit disable of external entity resolution is found in parser configuration
Your environment is affected if the unstructured library version is 0.14.2 or lower AND your application uses XMLParser to process untrusted XML files with default settings.
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 dataUpdate unstructured to a version newer than v.0.14.2, or disable external entity resolution in the XMLParser configuration if upgrading is not immediately feasible.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46455 — 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-2024-46455 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