Policy bypass via lossy federated-principal flattening
Published Jul 24, 2026 · Updated Jul 24, 2026
Incorrect comparison in @hulumi/policies before 1.4.0 allows attackers to bypass IAM-role checks via multi-provider OIDC trusts. The federatedIsGithubOidc matcher coerces Principal.Federated arrays into a comma-joined string and checks only its start, so a later GitHub provider is missed. A role must trust multiple OIDC providers; wildcard subject conditions can then pass G_OIDC_1 and G_OIDC_2 validation and expose role assumption or administrator-level permissions.
Summary
What happened
Incorrect comparison in @hulumi/policies before 1.4.0 allows attackers to bypass IAM-role checks via multi-provider OIDC trusts. The federatedIsGithubOidc matcher coerces Principal.Federated arrays into a comma-joined string and checks only its start, so a later GitHub provider is missed. A role must trust multiple OIDC providers; wildcard subject conditions can then pass G_OIDC_1 and G_OIDC_2 validation and expose role assumption or administrator-level permissions.
The record
- CVE
- CVE-2026-48032
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- Sherif Mansour
- Product
- Hulumi
- Classifications
- CWE-697, T1078.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 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=< 1.4.0
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.
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