AWS Fixes ssosync Privilege Inheritance from Reused Identities

P1 — VALIDATE AND UPDATEHigh · 8.5 (CVSS v3.1; AWS repository-owner advisory)EXPLOITATION: NOT STATED

Quick Answer

Upgrade ssosync to 2.9.5 or later and audit IAM Identity Center memberships and permission sets for identities whose email addresses or group names were reused.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify ssosync deployments, versions, forks, synchronization schedules, Google Workspace identity lifecycle owners and linked AWS accounts. Review identifier reassignment and reconciliation history. An email or group-name match is not sufficient proof that two records represent the same person or group. Deploy ssosync 2.9.5 or later and incorporate the fix in forks. AWS provides no workaround; correct any unexpected entitlements through approved access-management procedures. Test identity creation, deletion and controlled identifier reuse in a nonproduction environment. Verify expected group membership and permission sets; retain identity mappings, deployment records and access-review evidence.

Open the authoritative advisory

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

Scope And Authority

Product scopeAWS ssosync synchronization from Google Workspace to IAM Identity Center
Advisory2026-194-AWS / GHSA-8mf9-xp78-xr32
CVECVE-2026-133199
Authoritative release date2026-11-20T16:30:00Z — AWS bulletin publication at 08:30 PST; the repository-owner advisory followed at 16:38:53Z.
Authority revision dateNo separate material revision is stated for this release.
Affected versionsssosync versions before 2.9.5 when a reused Google Workspace email address or group name is matched to a previously synchronized identity.
Fixed versionssosync 2.9.5 or later, including the corresponding fixes in maintained forks and derivatives.
CVSS base score8.5 (CVSS v3.1; AWS repository-owner advisory)
CVSS severityHigh
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

AWS corrected reconciliation that could attach a reused Google Workspace email address or group name to an unrelated IAM Identity Center identity, preserving its group memberships and permission-set assignments. The attack requires an administrator to reassign the identifier within the synchronization schedule; the inheriting user need not have AWS permissions or Workspace administrator rights.

What To Validate Now

  1. Inventory. Identify ssosync deployments, versions, forks, synchronization schedules, Google Workspace identity lifecycle owners and linked AWS accounts.
  2. Establish applicability. Review identifier reassignment and reconciliation history. An email or group-name match is not sufficient proof that two records represent the same person or group.
  3. Remediate. Deploy ssosync 2.9.5 or later and incorporate the fix in forks. AWS provides no workaround; correct any unexpected entitlements through approved access-management procedures.
  4. Validate. Test identity creation, deletion and controlled identifier reuse in a nonproduction environment. Verify expected group membership and permission sets; retain identity mappings, deployment records and access-review evidence.
  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

The software fix does not establish that inherited permissions were removed or that historical account activity was reviewed. Preserve audit records before correcting entitlements.

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.