Skip to content
TrustList
Security advisories

AWS fixes ssosync access mix-up and a Document Loader MCP path flaw

Editorial

By TrustList Editorial

ssosync before 2.9.5 could hand a reused e-mail address the IAM Identity Center access of an old identity; Document Loader MCP Server 1.0.10 to 1.0.20 could read files outside its base directory.

About AWS fixes ssosync access mix-up and a Document Loader MCP path flaw

AWS fixes ssosync access mix-up and a Document Loader MCP path flaw

20 November 2026: Amazon Web Services has published two Important bulletins for open-source tools it maintains. The first, CVE-2026-133199, could let a new Google Workspace account inherit the AWS IAM Identity Center group memberships and permission sets of an unrelated person who once used the same e-mail address. The second, CVE-2026-130901, lets AWS's Document Loader MCP Server read files outside the directory it is meant to stay in. Neither has a workaround that removes the need to upgrade, and AWS asks anyone running a fork to patch it too.

Not yet independently verified. This rests on AWS's own two bulletins of 20 November 2026; neither flaw has a CVE.org record we could read yet or an independent report, and neither is listed as exploited. We will update this when it can be confirmed, and remove this note.

How ssosync could hand out someone else's access

ssosync copies users and groups from Google Workspace into IAM Identity Center. Its reconciliation logic first tries to match each account or group by its immutable identifier. When that failed, versions before 2.9.5 fell back to matching by e-mail address or group name and updated the existing Identity Center record in place. A reused address, such as one handed to a new starter after the previous holder left, could therefore pick up the old holder's group memberships and permission set assignments in AWS.

The fix is ssosync 2.9.5, and the bulletin, published at 08:30 Pacific time, says there is no workaround. AWS also asks users to confirm that their Identity Center group memberships and permission set assignments are as expected, which is the step that catches access already inherited before the upgrade. The issue is tracked as GHSA-8mf9-xp78-xr32, and AWS credits George Chen.

A base directory that was not enforced

Document Loader MCP Server is a Model Context Protocol server that lets AI assistants parse PDF, Office and image files on the local file system. In versions 1.0.10 to 1.0.20, when DOCUMENT_BASE_DIR is unset or empty and the server runs with continuous integration or test environment variables present, its default base-directory restriction is not enforced. Someone who can influence the documents an MCP client processes could make it read supported files outside the intended folder, and in 1.0.12 to 1.0.20 also write PNG slide images to other directories.

Version 1.0.21 fixes it. Until then, AWS says to set DOCUMENT_BASE_DIR to the folder that holds the documents, and not to "/", which removes the restriction. Rishaank Gupta reported it.

Where these tools turn up

ssosync is usually run by a platform or identity team as a scheduled job, so it is easy to miss in a software inventory; a search of deployment pipelines for the tool name is a quicker check than waiting for a scanner. The MCP server is more likely to sit on developer machines and in agent test rigs, where CI variables are exactly the condition the bulletin describes. Both are worth adding to the list of open-source components that change who can see what.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in