Skip to main content
Menu
CVEs

Amazon Document Loader MCP Server file read outside base directory in path restriction

CVE-2026-130901Published , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.21
Who is exposed
Not reported

Summary

The Amazon document-loader-mcp-server has a path restriction flaw that lets a local attacker read files outside its intended base directory, and in some releases also write PNG slide images outside it. The attacker needs no login but must get a user to process crafted document content through an MCP client.

Written by a model

Original description

Improper limitation of a pathname to a restricted directory in the file access checks in Amazon awslabs.document-loader-mcp-server 1.0.10 through 1.0.20 might allow a context-dependent actor, via crafted document content processed by an MCP client, to read files outside the intended base directory and, in 1.0.12 through 1.0.20, to write PNG slide images outside it. This occurs when DOCUMENT_BASE_DIR is not set or is empty and the CI, GITHUB_ACTIONS or PYTEST_CURRENT_TEST environment variable is present. Versions before 1.0.10 do not restrict file access to a base directory.

To remediate this issue, users should upgrade to version 1.0.21 or later. Users who cannot upgrade immediately can set DOCUMENT_BASE_DIR to the directory that holds their documents. Do not set it to /, which removes the restriction.

What to do

Upgrade to a fixed version: 1.0.21.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130901 (Improper limitation of a pathname to a restricted directory in Amazon awslabs.document-loader-mcp-server), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130901 (entry last updated 2026-11-20):
Affected:
- Amazon document-loader-mcp-server: from 1.0.10, fixed in 1.0.21
Fixed versions: 1.0.21.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130901 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130901 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://aws.amazon.com/security/security-bulletins/2026-195-aws/
- https://pypi.org/project/awslabs.document-loader-mcp-server/1.0.21/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130901
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130901"}.

Affected versions

cve.now Index

5Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisoryaws.amazon.com · security/security-bulletins/2026-195-aws
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130901
RecordNVD · CVE-2026-130901
Other links 1
Patchpypi.org · project/awslabs.document-loader-mcp-server/1.0.21

Questions about CVE-2026-130901

Is CVE-2026-130901 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-130901?

document-loader-mcp-server: from 1.0.10 before 1.0.21.

Source: cve.now feed data

How do I fix CVE-2026-130901?

Upgrade to a fixed version: 1.0.21.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.