CVE-2026-133199: AWS ssosync · Incorrect Privilege Assignment
Affects AWS ssosyncSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 2.9.5 soon.
Data as of 20 Nov 2026, 17:19 UTC
Thin evidence
One scorer or none| CNA (AMZN) | CVSS 3.1 | 8.5 |
|---|---|---|
| CNA (AMZN) | CVSS 4.0 | 5.8 |
- Patch
- Available – fixed in 2.9.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 24 Oct 2026.
What to do
Upgrade ssosync and awslabs/ssosync to 2.9.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSssosync | Affected
| Fixed in
|
GitHubawslabs/ssosyncpkg:github/awslabs/ssosyncOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade AWS ssosync to version 2.9.5 or later, where this privilege assignment issue is fixed. Since this is a cloud service, AWS manages remediation for the cloud-hosted components, but customers must update their ssosync instances accordingly. No other mitigations are specified.
Description
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.