CVE-2026-48034: @hulumi/policies has a HULUMI-H5 bypass via decoy sibling resources targeting a different bucket
Affected: @hulumi/policies < 1.4.0 — Fixed in: 1.4.0 — Severity: High — CWE-284 (Improper Access Control) Summary HULUMI-H1 forbids raw aws:s3:Bucket outside of Hulumi's SecureBucket component, with one exemption: a raw bucket that's a child of a SecureBucket is allowed because the component is responsible for the hardening.
Published Jun 10, 2026
Affected packages
@hulumi/policies
- Ecosystem
- npm
- Affected
- < 1.4.0
- Fixed in
- 1.4.0
- Check
npm ls @hulumi/policies
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Affected: @hulumi/policies < 1.4.0 — Fixed in: 1.4.0 — Severity: High — CWE-284 (Improper Access Control)
Summary
HULUMI-H1 forbids raw aws:s3:Bucket outside of Hulumi's SecureBucket component, with one exemption: a raw bucket that's a child of a SecureBucket is allowed because the component is responsible for the hardening. HULUMI-H5 is the defence-in-depth check that closes the H1 exemption — for any raw bucket claiming it, H5 verifies the five hardening sibling resources a real SecureBucket always emits (public-access block, SSE-KMS, ownership controls, versioning, TLS-only bucket policy) are actually present.
The bug: H5 only checked the siblings' _types_. It never verified that those siblings actually applied to the bucket being exempted. A consumer (or compromised PR) could pair an unhardened raw bucket with five hardening sibling resources whose bucket property pointed at a _completely different_ bucket, and H5 would report no violation while the actual bucket shipped with zero hardened defaults.
Impact
Consumers using HulumiHardeningPack could ship a raw S3 bucket with no public-access block, no SSE-KMS, no ownership controls, no versioning, and no TLS-only bucket policy — while the policy pack reported the stack as compliant.
Patches
Upgrade to @hulumi/[email protected]. The H5 sibling check now requires both (a) the sibling to share the same parent SecureBucket instance via the anchored URN helper from GHSA-2, AND (b) the sibling's bucket property — or, for the bucket policy, its Resource ARN list — to reference the exempted bucket explicitly. Five decoy siblings pointing at a different bucket no longer count.
Workarounds
None — the exemption itself is the mechanism, so the value-binding check is the only fix.
Resources
Credited to kerberosmansour.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-48032
@hulumi/policies bypasses IAM-role policy checks when the role trusts multiple OIDC providers
high8.3Jun 10, 2026CVE-2026-48033
@hulumi/policies bypasses policy packs with a forged Pulumi-URN logical name
high8.4Jun 10, 2026GHSA-4xrh-5m3m-328w
@hulumi/policies: CIS 1.16 admin policy bypass for inline and attached IAM policies
high8.7May 21, 2026GHSA-59f3-7227-wmh4
@hulumi/policies: Stack-wide evidence bypassed Cloudflare and deployment-governance guardrails
high8.7May 21, 2026GHSA-g43v-9x7q-83pq
@hulumi/policies: HULUMI-H1 SecureBucket parent spoof bypass
high8.7May 21, 2026GHSA-q2f7-m237-v562
@hulumi/policies: GitHub OIDC trust policy bypass via AWS set-qualified condition operators
critical9.3May 21, 2026
