Mend.io Vulnerability Database
The largest open source vulnerability database
What is a Vulnerability ID?
New vulnerability? Tell us about it!
CVE-2026-48034
Published:June 10, 2026
Updated:June 15, 2026
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/policies@1.4.0". 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 - "PR #178" (https://github.com/kerberosmansour/hulumi/pull/178) (Cluster B); decoy-sibling regression cases in "packages/policies/tests/hulumi-hardening-pack.test.ts". Supersedes "PR #175" (https://github.com/kerberosmansour/hulumi/pull/175), which had addressed the value-binding half but on a stale base.
Affected Packages
https://github.com/kerberosmansour/hulumi.git (GITHUB):
Affected version(s) >=v1.2.0 <v1.4.0
Fix Suggestion:
Update to version v1.4.0
@hulumi/policies (NPM):
Affected version(s) >=1.2.0 <1.4.0
Fix Suggestion:
Update to version 1.4.0
Do you need more information?
Contact Us
CVSS v4
Base Score:
8.5
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
HIGH
Subsequent System Integrity
HIGH
Subsequent System Availability
LOW
CVSS v3
Base Score:
7.7
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
Improper Access Control
EPSS
Base Score:
0.04