Skip to content
Cloud

CVE-2026-82857

9.3
Critical
EPSS 0.28%Patch availableSep 1, 2026

Privilege escalation in hulumi IAM policy allows creation of persistent higher‑privilege roles.

common questions

Is CVE-2026-82857 being exploited?

Not confirmed. CVE-2026-82857 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-82857?

CVE-2026-82857 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-82857?

Yes. A fix has been recorded for CVE-2026-82857. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-82857 affect?

CVE-2026-82857 affects hulumi < v1.3.2, weekly integration IAM policy, sandbox accounts using af-e2e-* roles. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82857?

Upgrade to hulumi v1.3.2, tighten IAM role boundaries, revoke/rotate affected roles and credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
hulumi < v1.3.2weekly integration IAM policysandbox accounts using af-e2e-* roles
impact

An attacker with the documented principal can create persistent af-e2e-* high‑privilege roles in sandbox accounts, enabling long‑term privileged access and lateral movement.

action required

Immediate action required

affected versions
kerberosmansour hulumi
  • affected< 1.3.2
vendor says fixed in1.3.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free