Authenticated privilege escalation via approver injection
Published Mar 4, 2025 · Updated Oct 14, 2025
Improper authorization in AWS TEAM before 1.2.2 allows remote authenticated users to self-approve eligible access requests. The GraphQL API accepts a requester-controlled approver field without enforcing field-level authorization, allowing approval to be spoofed. The user must already be onboarded to the requested role; the flaw does not grant access to roles for which that user is ineligible.
Summary
What happened
Improper authorization in AWS TEAM before 1.2.2 allows remote authenticated users to self-approve eligible access requests. The GraphQL API accepts a requester-controlled approver field without enforcing field-level authorization, allowing approval to be spoofed. The user must already be onboarded to the requested role; the flaw does not grant access to roles for which that user is ineligible.
The record
- CVE
- CVE-2025-1969
- Published
- Mar 4, 2025
- Updated
- Oct 14, 2025
- Vendor
- Amazon Web Services
- Product
- Temporary Elevated Access Management (TEAM)
- Classifications
- T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo