Skip to main content
VulnerabilityPublished

CVE-2026-130901: AWS document-loader-mcp-server · Path Traversal

Affects AWS document-loader-mcp-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.0.21 when convenient.

Data as of 20 Nov 2026, 19:14 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (AMZN)CVSS 3.15.3
CNA (AMZN)CVSS 4.05.8
Patch
Available – fixed in 1.0.21
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade AWS document-loader-mcp-server to 1.0.21.

Affected software

ProductAffectedFixed in
Amazondocument-loader-mcp-serverAffected
  • >=1.0.10 <1.0.21
Fixed in
  • 1.0.21

AI-suggested

A fix is available in version 1.0.21. Users should upgrade to version 1.0.21 or later to remediate this vulnerability. For users unable to upgrade immediately, setting the DOCUMENT_BASE_DIR environment variable to the directory holding their documents will mitigate the issue. It is critical not to set DOCUMENT_BASE_DIR to the root directory (/) as this removes the restriction and leaves the system vulnerable.

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.

Reports on CVE-2026-130901

References

Community reviews

Loading reviews…