IAM boundary bypass via unconstrained role tagging
Published Aug 31, 2026 · Updated Aug 31, 2026
Improper access control in Hulumi before 1.3.2 allows remote attackers to bypass IAM boundaries through a deployment SCP template. The template does not constrain tag-on-create use of the hulumi:iac-role marker, so attacker-controlled resources can satisfy its trusted-role condition. Exposure requires a downstream AWS deployment that imported the pre-1.3.2 template and relies on that tag as its IAM boundary.
Summary
What happened
Improper access control in Hulumi before 1.3.2 allows remote attackers to bypass IAM boundaries through a deployment SCP template. The template does not constrain tag-on-create use of the hulumi:iac-role marker, so attacker-controlled resources can satisfy its trusted-role condition. Exposure requires a downstream AWS deployment that imported the pre-1.3.2 template and relies on that tag as its IAM boundary.
The record
- CVE
- CVE-2026-82859
- Published
- Aug 31, 2026
- Updated
- Aug 31, 2026
- Vendor
- Sherif Mansour
- Product
- Hulumi
- Classifications
- CWE-284, T1098.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2026CVE publishedPublication date reported by the CVE source.
- Aug 31, 2026Record 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.3.2
What conditions does exploitation require?
What is affected?
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.
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