AWS ssosync privilege escalation in user and group reconciliation
- Exploited
- No known exploitation
- Fix
- Fixed in 2.9.5
- Who is exposed
- Specific setups only
Summary
AWS ssosync has an incorrect privilege assignment flaw in its user and group reconciliation logic. When a reused Google Workspace e-mail address or group name is synchronized, it can give the account a previously synchronized, unrelated identity's group memberships and permission set assignments. An attacker can reach it remotely over the network after logging in with low privileges.
Written by a model
Original 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.
What to do
Upgrade to a fixed version: 2.9.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133199 (Incorrect privilege assignment on reused e-mail addresses or group names in AWS ssosync), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133199 (entry last updated 2026-11-20):
Affected:
- AWS ssosync: fixed in 2.9.5
Fixed versions: 2.9.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133199 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133199 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://aws.amazon.com/security/security-bulletins/2026-194-aws/
- https://github.com/awslabs/ssosync/releases/tag/v2.9.5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133199
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133199"}.Affected versions
- AWS ssosyncfixed in 2.9.5
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | aws.amazon.com · security/security-bulletins/2026-194-aws |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133199 |
| Record | NVD · CVE-2026-133199 |
| Other links 1 | |
| Patch | GitHub · awslabs/ssosync · Release v2.9.5 |
Questions about CVE-2026-133199
Is CVE-2026-133199 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
When an e-mail address or group name is reused, ssosync can make a new identity inherit the IAM Identity Center group memberships and permission set assignments of a previously synchronized, unrelated identity.
Source: aws.amazon.com
Which versions are affected by CVE-2026-133199?
ssosync: before 2.9.5.
Source: cve.now feed data
Am I affected, and how do I check?
The affected range is ssosync versions before 2.9.5, and no specific configuration conditions are listed. To check a deployment, compare the ssosync version it runs against 2.9.5.
Source: aws.amazon.com
How do I fix CVE-2026-133199?
Upgrade ssosync to version 2.9.5, which the advisory says addresses this issue.
Source: aws.amazon.com
Related
- CVE-2026-122193OS command injection in the example SSM documents in Trusted Remote Execution (REX)
- CVE-2026-119923Heap-based Buffer Overflow in Babelfish for PostgreSQL TDS Prelogin Parser
- CVE-2026-100307Missing authorization on the external management API in mcp-gateway-registry enables privilege escalation to registry administrator
- CVE-2026-126087Untrusted search path in the cross-user process launcher in OpenJD Sessions for Python, as used in the AWS Deadline Cloud worker agent
- CVE-2026-122266Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS
- CVE-2026-125926Server-side request forgery in the server registration and update API in mcp-gateway-registry
No corrections so far. Something wrong on this page? Report an error.