Security / News explained
Reused identities need a fresh privilege decision
AWS’s November 20 ssosync disclosure explains how reused email addresses or group names could inherit earlier access. Version 2.9.5 fixes the issue; existing assignments still need review.
AWS’s November 20, 2026 bulletin describes an identity mix-up with an awkward consequence: a reused email address or group name could bring somebody else’s AWS access along with it. CVE-2026-133199 affects ssosync versions before 2.9.5. AWS identifies 2.9.5 as corrected and asks operators to review existing group memberships and permission-set assignments. [1]
The affected component is ssosync, the open-source tool that synchronizes Google Workspace users and groups into AWS IAM Identity Center. The project advisory concerns that synchronization relationship. Simply using Google Workspace or IAM Identity Center does not establish that an organization runs the affected tool or has encountered this identity-reuse scenario. [2]
The dates deserve their own sentence. The project’s v2.9.5 release was published on October 28, 2026; the vulnerability disclosure followed on November 20. This is newly published security context about an already available release. The release timestamp alone cannot tell an operator which version an existing deployment actually runs. [4]
A familiar address can belong to a different person
AWS describes the faulty fallback precisely. If a Workspace account or group did not match an existing IAM Identity Center identity by its immutable identifier, ssosync matched by email address or group name and updated the existing identity in place. The earlier identity’s access could therefore survive the change of occupant. [1]
Identity standards explain why that distinction matters. RFC 7643 defines a SCIM resource’s service-provider-issued id as stable and non-reassignable. It separately defines externalId as a provisioning-client identifier. That is a useful design distinction, rather than a claim that every field called an external ID automatically has identical lifecycle guarantees. [5]
Consider a hypothetical finance employee who leaves and whose address is later assigned to a new starter. People recognize the familiar mailbox; the directory recognizes a different account. If a synchronization process treats that address as proof that the old identity continues, previously approved access may follow the label. An address book has quietly become an authorization policy, which is rather more responsibility than it applied for.
The project advisory gives the necessary setup: a Workspace administrator must reassign a previously synchronized email address or group name that held Identity Center entitlements, within the synchronization schedule. The authenticated user who receives that address, or belongs to that reused group, need not have AWS permissions or Workspace administrator rights beforehand. [2]
Our reading is that routine directory administration is part of the risk path. A carefully approved decision to reuse a name can still have an unintended downstream effect. That makes the handoff between identity administration and cloud-access administration more significant than either team’s screen might suggest on its own.
The fix and the access review answer different questions
Amazon’s CNA record agrees with the project’s version boundary: ssosync before 2.9.5 is affected, and remediation is 2.9.5 or later. An upgrade addresses the vulnerable software version. Forks and packaged copies deserve attention too, because a familiar deployment name does not prove which implementation is running. [3]
The v2.9.5 documentation also describes an explicit assignment-preservation option, force-externalid-update. It can update an existing user’s external identifier in place when the email matches but the identity differs. The documentation warns that enabling it can preserve an unrelated user’s privileges, and frames its use around a controlled identity-provider migration. [6]
That documentation separately describes adoption of an email-matched user with no external identifier set. These are reasons to review actual matching and migration choices alongside the package version. We would treat deliberate privilege preservation as an explicit access decision whose owner can explain which continuing person or group it represents. [6]
AWS’s additional instruction to confirm memberships and permission-set assignments is consequential. A software update and a review of already stored access answer separate operational questions. The bulletin supplies no workaround, and it does not promise that installing the fixed release automatically removes every earlier incorrect assignment. [1]
For a hypothetical group renamed back to an old department name, the useful question is who its members should be entitled to act as today. The same spelling is weak evidence of continuity. A current access decision needs a current business owner, especially where the old group’s purpose has changed.
Keep continuity deliberate
The broader engineering lesson is about the meaning of a match. Labels help people find things; durable identity links help systems decide whether a thing is still the same thing. When a mismatch is silently repaired through a friendly label, convenience can preserve authority that should have been reconsidered.
For teams running ssosync, the concrete consequence is a paired maintenance decision: use the corrected software and reconcile the access attached to reused identities. Keep the distinction between the source account, its visible label and its downstream entitlements visible in that discussion. Familiar names should make accounts easier to find, without deciding what their next occupant is allowed to do.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- AWS ssosync security bulletin 2026-194AWS · Checked Nov 21, 2026
- ssosync project advisory GHSA-8mf9-xp78-xr32AWS Labs · Checked Nov 21, 2026
- CVE-2026-133199 original CNA recordAmazon / CVE Program · Checked Nov 21, 2026
- ssosync v2.9.5 release metadataAWS Labs / GitHub · Checked Nov 21, 2026
- RFC 7643: SCIM Core Schema, common attributesIETF / RFC Editor · Checked Nov 21, 2026
- ssosync v2.9.5 documentation: preserving assignmentsAWS Labs · Checked Nov 21, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.