PT-2026-48474 · Npm+2 · @Hulumi/Policies+1
CVE-2026-48032
·
Published
2026-06-10
·
Updated
2026-07-27
CVSS v4.0
8.3
High
| Vector | AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N |
Name of the Vulnerable Software and Affected Versions
@hulumi/policies versions prior to 1.4.0
Description
IAM-role policy checks can be bypassed when a role trusts multiple OIDC (OpenID Connect) providers. The issue occurs when the
Principal.Federated field contains a JSON array of multiple providers; the system coerces this list into a single comma-joined string, causing the matcher to fail to recognize GitHub Actions as one of the providers. Consequently, the G OIDC 1 and G OIDC 2 policy rules skip necessary wildcard checks for sub: conditions. This allows IAM roles with overly permissive conditions—which could let untrusted pull requests from forks assume the role—to be reported as compliant. Additionally, the G OIDC 2 detector fails to perform blast-radius checks for cluster-admin or AdministratorAccess permissions in these scenarios.Recommendations
Upgrade @hulumi/policies to version 1.4.0.
Exploit
Fix
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
@Hulumi/Policies
Hulumi