# CVE-2026-82857: hulumi privilege escalation in weekly integration IAM policy

Source: https://junglewise.ai/threats/cve-2026-82857-hulumi-privilege-escalation-in-weekly-integration-iam-policy  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-31. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-82857 · Severity: critical · CVSS 9.8 · Published 2026-08-31

hulumi is a tool for managing AWS IAM roles and policies in sandbox accounts. The documented weekly integration IAM policy contained overly permissive role lifecycle operations that allowed attackers to create higher-privilege roles, effectively bypassing access controls and gaining persistent elevated permissions in the sandbox environment.

Technologies: [Kerberosmansour Hulumi](https://junglewise.ai/threats/technologies/hulumi). Vendors: [Kerberosmansour](https://junglewise.ai/threats/vendors/kerberosmansour).

## Quick answers

**Is CVE-2026-82857 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-82857 being exploited in the wild.

**How severe is CVE-2026-82857?** Critical severity, with a CVSS score of 9.8, published 31 August 2026.

**Which products and versions are affected?** Kerberosmansour Hulumi before v1.3.2.

**Is there a fix for CVE-2026-82857?** A patch was published on 2026: Version v1.3.2 fixes the vulnerability Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-82857 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-82857?** Check whether you run Kerberosmansour Hulumi at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a privilege escalation (CWE-269) in the weekly integration IAM policy template shipped with hulumi versions before v1.3.2. The vulnerable policy allowed unnecessary inline-policy and trust-update permissions on af-e2e-* roles without sufficient boundary or trust restrictions. An attacker with access to a principal documented to use this policy could create persistent higher-privilege roles in the sandbox account. The vulnerability requires the attacker to already have the documented principal in place, making it more of a misconfiguration risk than an unauthenticated remote attack. The fix (v1.3.2) removes the unnecessary inline-policy and trust-update permissions and updates the published guide.

## Affected products

- kerberosmansour hulumi before v1.3.2

## Timeline

- 2026-05-15: disclosed: GitHub Security Advisory GHSA-35qr-vx94-m5x3 published
- 2026-08-31: advisory: NVD published CVE-2026-82857
- 2026: patched: Version v1.3.2 fixes the vulnerability

## References

- [https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-35qr-vx94-m5x3](https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-35qr-vx94-m5x3)
- [https://www.vulncheck.com/advisories/hulumi-before-1.3.2-privilege-escalation-via-iam-policy](https://www.vulncheck.com/advisories/hulumi-before-1.3.2-privilege-escalation-via-iam-policy)

## Related threats

- [Hulumi threat-model helper script shadowing vulnerability](https://junglewise.ai/threats/cve-2026-82862-hulumi-threat-model-helper-script-shadowing-vulnerability)
- [kerberosmansour Hulumi security policy bypass via decoy sibling resources](https://junglewise.ai/threats/cve-2026-48034-kerberosmansour-hulumi-security-policy-bypass-via-decoy-sibling)
- [kerberosmansour Hulumi policy bypass via forged Pulumi-URN logical name](https://junglewise.ai/threats/cve-2026-48033-kerberosmansour-hulumi-policy-bypass-via-forged-pulumi-urn)