Security / News explained
Document Loader MCP needs its directory boundary enforced
AWS’s November 20 disclosure describes a conditional file-directory restriction failure in Document Loader MCP Server. Version 1.0.21 corrects it, with a narrower PNG-write exposure also documented.
AWS disclosed CVE-2026-130901 on November 20, 2026, describing a directory restriction failure in Document Loader MCP Server versions 1.0.10 through 1.0.20. Under particular environment conditions, a document-processing workflow could reach supported files beyond its intended directory. AWS identifies version 1.0.21 as corrected. The environment conditions are central to understanding the exposure. [1]
This is the open-source AWS Labs MCP server for parsing documents and images on a local filesystem. Its documented tools extract document content, load images, and render presentation or PDF pages as PNG images. The component’s intended job already involves reading files, so the location boundary is a meaningful part of its contract. [3]
The fix was available before the disclosure. PyPI’s version-specific metadata records the 1.0.21 wheel and source archive being uploaded on September 1, 2026, in UTC. November 20 is the advisory date. These separate dates matter when deciding whether an older deployment has already received the relevant package change. [4]
The environment can change the boundary
Amazon’s CNA description names the combination: DOCUMENT_BASE_DIR is unset or empty, and CI, GITHUB_ACTIONS or PYTEST_CURRENT_TEST is present in the environment. In affected versions, the default directory restriction is then bypassed. The actor must be able to influence document content processed by an MCP client; the record does not describe every running server as automatically exploitable. [2]
The two operation ranges also differ. Reading supported files outside the intended directory concerns 1.0.10 through 1.0.20. Writing PNG slide images outside it concerns 1.0.12 through 1.0.20. Keeping those ranges and the PNG output type attached to the claim avoids turning a specific finding into a much broader, unsupported one. [1]
There is an older-version wrinkle: the CNA says versions before 1.0.10 did not restrict file access to a base directory. Falling outside the advisory’s listed regression range therefore does not establish that an earlier version supplies the desired containment. The documented remediation remains 1.0.21 or later. [2]
Imagine a hypothetical document assistant launched by a build job. Its owner expects a working folder to contain the material the assistant can inspect. The job also inherits a CI marker from its runner, while nobody sets a document directory explicitly. That combination makes an apparently incidental environment detail relevant to the older server’s access policy.
The practical implication is that a launch environment belongs in the security discussion. A developer’s interactive session and a scheduled worker can run the same package with different inherited settings. A successful document extraction demonstrates useful functionality; by itself, it says little about whether an out-of-directory request would be denied.
The advisory’s read claim is limited to supported files, and its write claim is limited to PNG slide images. It does not establish arbitrary binary-file disclosure, arbitrary file writes or code execution. Those distinctions remain useful even when prioritizing the update: precision helps identify which workflows actually need attention. [2]
An explicit directory makes the intention visible
The 1.0.21 package documentation describes DOCUMENT_BASE_DIR as constraining resolved paths for read_document, read_image and both input and output paths of extract_slides_as_images. It says the default is the current working directory and that enforcement continues under CI and test markers. Here, the documented protection is a file-directory boundary; it should not be read as a guarantee of complete operating-system isolation. [3]
AWS’s temporary measure, for operators who cannot upgrade immediately, is to set DOCUMENT_BASE_DIR explicitly to the directory holding the documents. Its warning is equally specific: setting that value to the filesystem root, /, removes the restriction. The intended directory has to be meaningfully narrower than everything the process can see. [1]
Our interpretation is that an explicit value helps make the intended scope reviewable. A working directory chosen by a launcher may be perfectly reasonable, yet still be broader than the document collection someone had in mind. Naming the document collection directly gives the operator and the application owner the same concrete boundary to discuss.
That boundary also lives alongside the permissions of the process running the server. A directory check and operating-system access controls answer different questions: which paths the tool accepts, and which resources its process can reach. Giving a document worker only the files needed for its job keeps the surrounding design easier to understand.
Treat content and configuration as separate inputs
The revealing feature of this disclosure is how ordinary the ingredients look: a document, an omitted setting, and an environment marker associated with testing. None needs to look dramatic in isolation. Their interaction is what matters. A test marker is a useful label, but it should not accidentally become a hall pass.
For teams operating this server, the useful outcome is a clear account of the installed version, the launch environment and the intended document directory. The vendor’s fixed-version guidance supplies the software decision. The remaining engineering judgment is to keep document content from quietly expanding the authority of the process asked to interpret it.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- Document Loader MCP security bulletin 2026-195AWS · Checked Nov 21, 2026
- CVE-2026-130901 original CNA recordAmazon / CVE Program · Checked Nov 21, 2026
- Document Loader MCP Server 1.0.21 documentationAWS Labs / PyPI · Checked Nov 21, 2026
- Document Loader MCP Server 1.0.21 release metadataPyPI · Checked Nov 21, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.