CVE-2026-82857
CriticalCVSS 9.8Summary
A privilege escalation vulnerability in hulumi before v1.3.2 exists in the weekly integration IAM policy, allowing role lifecycle operations on af-e2e-* roles without sufficient boundary restrictions. Attackers with the documented principal can create persistent higher-privilege roles in the sandbox account.
Risk Assessment
Risk of unauthorized privilege escalation and persistent takeover of the sandbox account, potentially compromising the integrity of the test environment.
Recommendation
Update hulumi to version 1.3.2 or later and review existing af-e2e-* roles for unauthorized changes.
Other vulnerabilities in hulumi
See all- CVE-2026-82862High
Hulumi versions before v1.3.2 resolve the threat-model helper script from an unsafe root, allowing workspace files to shadow the intended helper script. Attackers can place malicious files in the workspace to execute arbitrary code during local skill execution.
- CVE-2026-82859Critical
hulumi before v1.3.2 contain a deployment SCP template that allows tag-on-create bypasses for hulumi:iac-role protections. Attackers can bypass intended IAM boundary restrictions by exploiting the weakened SCP template in downstream deployments.
- CVE-2026-48037Medium
Hulumi prior to version 1.4.0 contains a vulnerability where AccountFoundation reuse paths silently downgrade GuardDuty / Security Hub posture. This issue has been patched in version 1.4.0.
- CVE-2026-48036High
In Hulumi prior to version 1.4.0, drift detection in CI/cron could silently cache transient adapter failures as 'all clear', masking real attacks for up to six hours, or falsely escalate ordinary provider-version churn to incident severity.
- CVE-2026-48035High
In Hulumi prior to version 1.4.0, users of AccountFoundation could deploy an AWS account whose CloudTrail/Config audit logs were deletable by any S3-delete-capable principal, despite the startup-hardened tier guaranteeing tamper-resistance. Sandbox deployments had no audit immutability.
- CVE-2026-48034High
In Hulumi prior to version 1.4.0, there is a bypass via decoy sibling resources targeting a different bucket.
- CVE-2026-48033High
In Hulumi prior to version 1.4.0, policy packs can be bypassed by a forged Pulumi-URN logical name.
- CVE-2026-48032High
In Hulumi prior to version 1.4.0, IAM-role policy checks can be bypassed when the role trusts multiple OIDC providers.
Original NVD description (English source)
hulumi versions before v1.3.2 contain a privilege escalation vulnerability in the weekly integration IAM policy that allows role lifecycle operations on af-e2e-* roles without sufficient boundary restrictions. Attackers with the documented principal can create persistent higher-privilege roles in the sandbox account.