Document Loader MCP: verify which files the agent can reach
A document tool needs to respect the approved directory in each environment. The AWS advisory guides a review of versions, configuration and access tests using fictional files.
Читать на португальскомIn this article
By Pentesty
Understand the combination described in the advisory
The November 20 AWS bulletin describes CVE-2026-130901 in Document Loader MCP 1.0.10 through 1.0.20 when DOCUMENT_BASE_DIR is absent or empty and CI or test variables are present. An actor influencing client-processed documents may read supported files outside the intended directory; versions 1.0.12 through 1.0.20 may also write PNG slide images externally.
AWS identifies 1.0.21 as the first fixed version. Its PyPI release page records September 1, 2026, before the bulletin disclosure. This analysis is dated November 22 and proposes an acceptance process for the organization’s own environment.
Locate the process that actually serves the client
List integrations using this package and the person responsible for each document workflow. Connect the MCP client, Python environment, installed version, startup method and process identity. Include developer workstations and continuous integration runners where they form part of the service. Configuration reviewed in a repository needs to match the configuration actually loaded.
Record the effective DOCUMENT_BASE_DIR value and the presence of CI or test variables without collecting unrelated sensitive values. Identify where approved documents enter the workflow. This record helps distinguish an installation covered by the advisory from one requiring further investigation, without assuming that every MCP integration behaves in the same way.
Make the approved directory a test criterion
Choose a test document directory and two fictional files of the same supported format: one inside it and one outside. Agree in advance which read should succeed and which should be denied. Perform the check only in an authorized environment with synthetic data, rather than searching real organizational documents to demonstrate the boundary.
If the workflow extracts slides, include a permitted PNG output and an external output that should be refused. Record the requested path, expected outcome and observed response. The analysis of upload write containment complements this planning: the destination needs to remain connected to the service’s authorization throughout document processing.
Connect the update to the running artifact
Choose an approved fixed version for the environment and record the package, origin, hash and functional test results. Restart the process through the deployment procedure, then check the version and loaded configuration again. Comparing dependencies across MCP restarts helps document differences that a configuration file alone may leave out of the acceptance record.
If an upgrade must wait, the vendor’s guidance is to set DOCUMENT_BASE_DIR explicitly to the document directory, never to /. Manage this as an exception with an owner and a deadline. For derivative code or forks, confirm that the running artifact incorporates the fix; changing a declared version number alone does not demonstrate that incorporation.
Close the change with evidence and an owner
Ask the workflow owner to review document reads, slide outputs where applicable and any functional differences. Record which environments were assessed and which remained outside scope. Keep minimal evidence such as version, effective directory, service identity, time and outcome, while avoiding the retention of document contents in test records.
Review process permissions and directories made available to the service as additional containment controls. Assign responsibility for unexpected denials and integration changes after deployment. Keep an approval record that lets the team repeat the assessment whenever the package, service identity or approved directory changes.
Frequently asked questions
Is every installation of these versions exposed?
The advisory describes combined version, directory and environment conditions. Check the running process and document inputs before deciding how it applies to an installation.
How should we choose the target version?
Check the bulletin and select a fixed version approved for your environment. Record compatibility, package origin and the artifact actually deployed.
How can we test without real documents?
Use fictional files in a supported format, inside and outside the approved directory. Define expected outcomes and stop if the test exceeds the authorized environment.
What demonstrates acceptance of the fix?
Connect the effective version and configuration to authorized checks of allowed and denied paths. Add functional results, scope, an owner and outstanding environments.
Sources and references
Original Pentesty analysis, published November 22, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.