Skip to content
Cloud

CVE-2026-48034

8.5
High
EPSS 0.26%Patch availableJul 25, 2026

Authorization bypass in Hulumi (<1.4.0) enabling cross-bucket access and potential RCE.

common questions

Is CVE-2026-48034 being exploited?

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

How severe is CVE-2026-48034?

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

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

What does CVE-2026-48034 affect?

CVE-2026-48034 affects Hulumi <1.4.0, Hulumi components for Pulumi, Pulumi deployments using Hulumi components, Cloud storage buckets targeted by Hulumi resources. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48034?

Upgrade to Hulumi v1.4.0; audit deployments, rotate credentials, review bucket permissions.

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

executive summary
technical analysis
affected
Hulumi <1.4.0Hulumi components for PulumiPulumi deployments using Hulumi componentsCloud storage buckets targeted by Hulumi resources
impact

Improper access control lets attackers manipulate sibling resources targeting other buckets, enabling unauthorized data access and possible code execution during provisioning.

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