AWS Fixes Document Loader MCP Server Directory Restrictions

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Upgrade Document Loader MCP Server to 1.0.21 or later. Until then, explicitly set DOCUMENT_BASE_DIR to the intended document directory, never to the filesystem root.

Confirm Scope And Apply The Supported Remediation

What to do now: Record the deployed package version, MCP clients, service identity, working directory, container mounts and CI or test environment variables. Check both the effective DOCUMENT_BASE_DIR setting and the environment inherited by the running process. Separate read access from the PNG-writing path introduced in 1.0.12. Install 1.0.21 or later and carry the fix into maintained forks. If an immediate upgrade is impossible, configure a specific document directory rather than / and restart through the normal deployment process. Test allowed documents and rejection of paths outside the approved directory. Retain version, environment and mount evidence; review unexpected file reads or writes where untrusted documents were processed.

Open the authoritative advisory

Last verified: 2026-11-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeawslabs.document-loader-mcp-server
Advisory2026-195-AWS
CVECVE-2026-130901
Authoritative release date2026-11-20 18:30:00 UTC
Authority revision dateNo separate material revision is stated for this release.
Affected versionsVersions 1.0.10 through 1.0.20 when DOCUMENT_BASE_DIR is unset or empty and CI or test environment variables are present. Reading supported files can escape the intended directory; versions 1.0.12 through 1.0.20 can also write PNG slide images outside it.
Fixed versionawslabs.document-loader-mcp-server 1.0.21 or later.
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not state that these vulnerabilities are being exploited in the wild.; no exploitation claim is inferred.

What Changed

AWS corrected a default-directory restriction that could be skipped in CI or test environments. An actor who influences documents processed by the MCP client could reach supported files outside the intended boundary. The vendor bulletin supplies no CVSS rating.

What To Validate Now

  1. Inventory. Record the deployed package version, MCP clients, service identity, working directory, container mounts and CI or test environment variables.
  2. Establish applicability. Check both the effective DOCUMENT_BASE_DIR setting and the environment inherited by the running process. Separate read access from the PNG-writing path introduced in 1.0.12.
  3. Remediate. Install 1.0.21 or later and carry the fix into maintained forks. If an immediate upgrade is impossible, configure a specific document directory rather than / and restart through the normal deployment process.
  4. Validate. Test allowed documents and rejection of paths outside the approved directory. Retain version, environment and mount evidence; review unexpected file reads or writes where untrusted documents were processed.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Do not treat containerization alone as a directory boundary: mounted secrets and other supported files may remain accessible to the service account. Earlier versions are not established as safe by this advisory.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.