Skip to content
Cloud

CVE-2026-48032

8.3
High
EPSS 0.31%Patch availableJul 25, 2026

IAM role policy checks bypass in Hulumi when role trusts multiple OIDC providers

common questions

Is CVE-2026-48032 being exploited?

Not confirmed. CVE-2026-48032 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.31% probability of exploitation in the next 30 days.

How severe is CVE-2026-48032?

CVE-2026-48032 is rated High with a CVSS score of 8.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-48032?

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

What does CVE-2026-48032 affect?

CVE-2026-48032 affects Hulumi < 1.4.0, Pulumi deployments using Hulumi, Cloud IAM roles trusting multiple OIDC providers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48032?

Upgrade Hulumi to v1.4.0; audit IAM role trust policies and rotate credentials as needed.

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

executive summary
technical analysis
affected
Hulumi < 1.4.0Pulumi deployments using HulumiCloud IAM roles trusting multiple OIDC providers
impact

Bypasses IAM role policy checks allowing unauthorized access and privilege escalation to cloud resources via roles trusting multiple OIDC providers.

action required

Immediate action required

affected versions
kerberosmansour hulumi
  • affected< 1.4.0

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