CVE-2026-133199 in ssosync
Summary
by MITRE • 11/20/2026
Incorrect privilege assignment in the user and group reconciliation logic in AWS ssosync before 2.9.5 might allow an authenticated remote user who is assigned a reused Google Workspace e-mail address or group name to inherit the IAM Identity Center group memberships and permission set assignments of a previously synchronized, unrelated identity, via automatic synchronization of that Google Workspace account or group.
To remediate this issue, users should upgrade to version 2.9.5 or later.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified in AWS SSO Sync prior to version 2.9.5 represents a critical flaw in the identity reconciliation logic, specifically concerning how user and group attributes are mapped during synchronization from Google Workspace to IAM Identity Center. This issue stems from an incorrect privilege assignment mechanism that fails to adequately distinguish between distinct identities when their external identifiers overlap with previously synchronized entities. In enterprise environments utilizing single sign-on solutions, it is common for organizational changes such as employee departures or role transitions to result in the reuse of email addresses or group names within identity providers like Google Workspace. The synchronization tool was designed to automatically map these external attributes to internal IAM Identity Center groups and permission sets without sufficiently validating that the underlying unique user identifier remains consistent with previous associations, thereby creating a pathway for unauthorized privilege inheritance.
From a technical perspective, the core flaw lies in the reconciliation algorithm's reliance on mutable identifiers rather than immutable ones during the initial matching phase. When an authenticated remote user is assigned a Google Workspace email address or group name that was previously associated with another identity and subsequently synchronized to IAM Identity Center, the system incorrectly assumes continuity of ownership over those permissions. Consequently, the new account inherits all IAM Identity Center group memberships and permission set assignments linked to the old identity. This behavior violates fundamental security principles regarding least privilege and separation of duties, as it allows a user who has no legitimate business justification for certain access rights to gain them through administrative oversight or configuration drift in the upstream identity provider.
The operational impact of this vulnerability is severe, particularly in organizations with high turnover rates or dynamic group structures where email aliases are frequently recycled. An attacker possessing valid credentials for a reused Google Workspace account could potentially escalate privileges by leveraging inherited IAM roles that grant access to sensitive AWS resources, such as databases, storage buckets, or compute instances belonging to other departments or former employees. This scenario effectively bypasses intended access controls and audit trails, as the actions performed under the new identity would be attributed to it while technically carrying the permissions of a different entity. Such misattribution complicates forensic analysis and incident response efforts, making it difficult to determine whether an action was authorized for that specific user or if it resulted from this synchronization artifact.
This vulnerability aligns with CWE-269, which describes Improper Privilege Assignment, as well as CWE-754, related to the use of unusual or non-standard characters in identifiers leading to ambiguity. In terms of adversary tactics, this flaw facilitates lateral movement and privilege escalation within a cloud environment by exploiting identity management gaps rather than direct technical exploits against software vulnerabilities. It highlights the risks associated with automated synchronization tools that prioritize convenience over strict identity verification during reconciliation processes. Organizations relying on AWS SSO Sync must recognize that while automation reduces manual overhead, it also amplifies the consequences of configuration errors or upstream changes in identity providers if not properly constrained by robust validation logic.
To remediate this issue and mitigate further risk, organizations are strongly advised to upgrade AWS SSO Sync to version 2.9.5 or later immediately upon availability. This update addresses the underlying reconciliation logic flaws that allowed for incorrect privilege inheritance based on reused identifiers. In addition to upgrading, administrators should implement rigorous monitoring of IAM Identity Center audit logs to detect any anomalous permission assignments resulting from identity changes in Google Workspace. It is also recommended to review and restrict the reuse policies within Google Workspace where possible, ensuring that email addresses and group names are not recycled without a mandatory de-provisioning period or explicit administrative approval process. Regular audits of synchronized permissions against actual business requirements will help ensure that no residual privileges persist from decommissioned accounts or transferred roles.