CVE-2025-6984
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 langchain-ai/langchain project, specifically the EverNoteLoader component, is vulnerable to XML External Entity (XXE) attacks due to insecure XML parsing. The affected version is 0.3.63. The vulnerability arises from the use of etree.iterparse() without disabling external entity references, which can lead to sensitive information disclosure. An attacker could exploit this by crafting a malicious XML payload that references local files, potentially exposing sensitive data such as /etc/passwd.
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 confidenceThe EverNoteLoader component in langchain versions 0.3.63 uses etree.iterparse() to parse XML without disabling external entity references, allowing XXE attacks where malicious XML payloads can reference local files (e.g., /etc/passwd) and exfiltrate sensitive data.
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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 langchain versionRun `pip show langchain` or check your dependency lock file to determine the installed version of langchainAffected if Installed version is exactly 0.3.63 or within the affected range around 0.3.63
-
Verify EverNoteLoader is in useSearch your codebase for imports or usage of `EverNoteLoader` from langchain (e.g., `from langchain_community.document_loaders import EverNoteLoader`)Affected if EverNoteLoader is imported or instantiated in your code
-
Confirm XML parsing occurs with user-supplied Evernote filesReview code paths where EverNoteLoader loads .enex XML files from external or untrusted sourcesAffected if EverNoteLoader processes XML files from user input, network sources, or untrusted locations
-
Check if etree.iterparse is invoked without entity resolution disabledInspect langchain library code (document_loaders/evernote_loader.py) to verify iterparse is called without `resolve_entities=False`Affected if The XML parser has external entity resolution enabled (default behavior)
-
Identify exposure to untrusted XML inputDetermine whether Evernote files processed by EverNoteLoader originate from users, APIs, or other untrusted sourcesAffected if Untrusted or attacker-controlled XML content is parsed by EverNoteLoader
You are affected if you use langchain version 0.3.63 with EverNoteLoader to parse XML files from untrusted or external sources, and the XML parser has external entity resolution enabled (default setting).
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 dataDisable external entity resolution in XML parsing by configuring the parser with resolve_entities=False or using a safe XML library like defusedxml to prevent XXE exploitation.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6984 — 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-6984 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