CVE-2026-48033: kerberosmansour Hulumi policy bypass via forged Pulumi-URN logical name

CVE-2026-48033 · Severity: high · CVSS 4 · Published 2026-07-24

Hulumi is a toolkit used to deploy secure cloud infrastructure using Pulumi. A security flaw allowed developers or malicious actors to bypass mandatory security checks (such as encryption or access controls) by carefully naming their cloud resources. This could result in the deployment of insecure infrastructure, such as unencrypted storage buckets or misconfigured network settings, while falsely appearing to comply with corporate security policies.

Technologies: Kerberosmansour Hulumi, @hulumi/policies (npm). Vendors: Kerberosmansour, npm.

Quick answers

Is CVE-2026-48033 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-48033 being exploited in the wild.
How severe is CVE-2026-48033?
High severity, with a CVSS score of 4, published 24 July 2026.
Which products and versions are affected?
Kerberosmansour Hulumi < 1.4.0; @hulumi/policies (npm) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0.
Is there a fix for CVE-2026-48033?
Yes. @hulumi/policies (npm): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48033 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-48033?
Check whether you run Kerberosmansour Hulumi or @hulumi/policies (npm) 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.

How to fix

  • @hulumi/policies (npm): upgrade to 1.4.0 or later
    npm install @hulumi/policies@1.4.0

Technical details

A protection mechanism failure (CWE-693) exists in @hulumi/policies prior to version 1.4.0. The toolkit identifies trusted parent components by performing substring matching on Pulumi Uniform Resource Names (URNs). Because Pulumi URNs include a developer-controlled logical name suffix, an attacker can inject trusted type strings (e.g., 'SecureBucket$') into the logical name to trick the policy engine into granting exemptions. This allows raw resources to bypass hardening rules for AWS S3, GitHub repositories, Cloudflare DNS, and CIS benchmarks. The vulnerability is resolved in version 1.4.0 by implementing structured URN parsing that anchors type-checks to the type-chain segment of the URN.

Affected products

  • kerberosmansour hulumi < 1.4.0
  • kerberosmansour @hulumi/policies < 1.4.0

Identifiers

  • CVE-2026-48033
  • GHSA-rhgj-6g2c-frmm

Timeline

  • 2026-05-19: patched: Fix merged in PR #178
  • 2026-05-20: advisory: GitHub Security Advisory published
  • 2026-07-24: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.