CVE-2026-48033: @hulumi/policies @hulumi/policies Bypasses Policy Packs With Vulnerability

HIGH
Advisory Identifier: GHSA-rhgj-6g2c-frmm
CWE-693
Published
Advisory Summary

CVE-2026-48033 is a HIGH @hulumi/policies bypasses policy packs with vulnerability (CWE-693: Protection Mechanism Failure) affecting @hulumi/policies libraries in the npm ecosystem. The issue involves @hulumi/policies bypasses policy packs with a forged pulumi-urn logical name. Remediation is available by upgrading affected packages to version 1.4.0.

CVE-2026-48033 at a Glance

CVE Identifier CVE-2026-48033
GHSA Identifier GHSA-rhgj-6g2c-frmm
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-693: Protection Mechanism Failure
Affected Product @hulumi/policies
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-48033

To remediate this vulnerability, upgrade all affected @hulumi/policies dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@hulumi/policies fixed: 1.4.0
npm install @hulumi/policies@1.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @hulumi/policies

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-48033, inspect your project dependencies using npm:

npm ls @hulumi/policies

Analyze the terminal output to locate any version of @hulumi/policies in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.4.0), your application is affected.

Note: The npm ls @hulumi/policies command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-693: Protection Mechanism Failure, where the product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. In @hulumi/policies, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**Affected:** `@hulumi/policies` `< 1.4.0` — **Fixed in:** `1.4.0` — **Severity:** High — **CWE-693 (Protection Mechanism Failure)** #### Summary Pulumi gives every cloud resource a structured URN that includes the resource's type chain (`hulumi:baseline:aws:SecureBucket$aws:s3/bucketV2:BucketV2`) and the _logical name_ the developer freely chose (anything after the final `::`). Several Hulumi policy rules used the URN to grant exemptions — for example, "if this raw bucket is a child of `SecureBucket`, skip the raw-bucket rule because the parent component handles hardening." The bug: the rules looked for a substring like `hulumi:baseline:aws:SecureBucket$` _anywhere_ in the URN. That substring can also appear in the developer-controlled logical-name portion. A developer (or compromised PR) could simply name a raw resource so its logical name carried the trusted substring, and every rule that used this check would treat the resource as if it were inside the trusted parent and skip its hardening check. Codex reported this for `DEPLOY_GOV_1`; the same anti-pattern existed in five more packs (unreported but identically exploitable): AWS H4/H5 sibling lookups, GitHub H1, GitHub H2, Cloudflare `CF_DNS_1`, Cloudflare `CF_DNSSEC_1`, and (advisory-level) CIS v5 §2.1.1 + §2.1.5. #### Impact Consumers using `@hulumi/policies` could ship raw `aws:s3:Bucket`, `github:Repository`, `cloudflare:Zone`, `cloudflare:DnsRecord`, and similar resources that bypassed mandatory hardening checks by naming themselves with a trusted substring. Every affected rule appeared to pass while the resource had none of the expected defaults. #### Patches Upgrade to `@hulumi/policies@1.4.0`. A new shared helper at `packages/policies/src/urn.ts` parses Pulumi URNs structurally and only looks for the trusted parent-type token inside the URN's type-chain segment — never inside the developer-controlled logical name. All six prior call sites have been migrated to it. #### Workarounds None reliable — a local lint that rejects logical names containing `$` would catch the trivial form of the spoof but not crafted variants. #### Resources - [PR #178](https://github.com/kerberosmansour/hulumi/pull/178) (Cluster B); the URN-anchoring refactor and per-pack spoof-vector regression tests in `packages/policies/tests/`.

CVE-2026-48033 Affected @hulumi/policies Versions

1 component(s)
Fixed Versions:
1.4.0
Product / Package Ecosystem Affected Versions Fixed Version
@hulumi/policies
npm
< 1.4.0
1.4.0

References

Frequently Asked Questions

What is CVE-2026-48033?
CVE-2026-48033 is a security vulnerability in @hulumi/policies involving @hulumi/policies bypasses policy packs with a forged Pulumi-URN logical name under CWE-693: Protection Mechanism Failure.
Which @hulumi/policies versions are affected?
Affected versions include releases prior to 1.4.0 across affected packages: @hulumi/policies.
What version fixes CVE-2026-48033?
Upgrading to 1.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @hulumi/policies affected?
Yes, @hulumi/policies is affected in releases prior to 1.4.0. Upgrade your dependency to 1.4.0 or later.
What CWE is associated with CVE-2026-48033?
CVE-2026-48033 is classified under CWE-693: Protection Mechanism Failure (The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.).
How can I check npm dependencies for CVE-2026-48033?
Run the dependency tree command: 'npm ls @hulumi/policies'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rhgj-6g2c-frmm",
  "modified" : "2026-06-10T13:37:38Z",
  "published" : "2026-06-10T13:37:38Z",
  "aliases" : [ "CVE-2026-48033" ],
  "summary" : "@hulumi/policies bypasses policy packs with a forged Pulumi-URN logical name",
  "details" : "**Affected:** `@hulumi/policies` `< 1.4.0` — **Fixed in:** `1.4.0` — **Severity:** High — **CWE-693 (Protection Mechanism Failure)**\n\n#### Summary\n\nPulumi gives every cloud resource a structured URN that includes the resource's type chain (`hulumi:baseline:aws:SecureBucket$aws:s3/bucketV2:BucketV2`) and the _logical name_ the developer freely chose (anything after the final `::`). Several Hulumi policy rules used the URN to grant exemptions — for example, \"if this raw bucket is a child of `SecureBucket`, skip the raw-bucket rule because the parent component handles hardening.\"\n\nThe bug: the rules looked for a substring like `hulumi:baseline:aws:SecureBucket$` _anywhere_ in the URN. That substring can also appear in the developer-controlled logical-name portion. A developer (or compromised PR) could simply name a raw resource so its logical name carried the trusted substring, and every rule that used this check would treat the resource as if it were inside the trusted parent and skip its hardening check.\n\nCodex reported this for `DEPLOY_GOV_1`; the same anti-pattern existed in five more packs (unreported but identically exploitable): AWS H4/H5 sibling lookups, GitHub H1, GitHub H2, Cloudflare `CF_DNS_1`, Cloudflare `CF_DNSSEC_1`, and (advisory-level) CIS v5 §2.1.1 + §2.1.5.\n\n#### Impact\n\nConsumers using `@hulumi/policies` could ship raw `aws:s3:Bucket`, `github:Repository`, `cloudflare:Zone`, `cloudflare:DnsRecord`, and similar resources that bypassed mandatory hardening checks by naming themselves with a trusted substring. Every affected rule appeared to pass while the resource had none of the expected defaults.\n\n#### Patches\n\nUpgrade to `@hulumi/policies@1.4.0`. A new shared helper at `packages/policies/src/urn.ts` parses Pulumi URNs structurally and only looks for the trusted parent-type token inside the URN's type-chain segment — never inside the developer-controlled logical name. All six prior call sites have been migrated to it.\n\n#### Workarounds\n\nNone reliable — a local lint that rejects logical names containing `$` would catch the trivial form of the spoof but not crafted variants.\n\n#### Resources\n\n- [PR #178](https://github.com/kerberosmansour/hulumi/pull/178) (Cluster B); the URN-anchoring refactor and per-pack spoof-vector regression tests in `packages/policies/tests/`.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@hulumi/policies"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-rhgj-6g2c-frmm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kerberosmansour/hulumi/pull/178"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kerberosmansour/hulumi"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-693" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-10T13:37:38Z",
    "nvd_published_at" : null
  }
}