{"id":"GHSA-9vc9-4jv3-rf86","revision":"31ab720f121949a090d2f220e3ab991b","records":[{"revision":"31ab720f121949a090d2f220e3ab991b","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-9vc9-4jv3-rf86","aliases":["CVE-2026-48034"],"title":"@hulumi/policies has a HULUMI-H5 bypass via decoy sibling resources targeting a different bucket","description":"**Affected:** `@hulumi/policies` `< 1.4.0` — **Fixed in:** `1.4.0` — **Severity:** High — **CWE-284 (Improper Access Control)**\n\n#### Summary\n\nHULUMI-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.\n\nThe 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.\n\n#### Impact\n\nConsumers 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.\n\n#### Patches\n\nUpgrade 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.\n\n#### Workarounds\n\nNone — the exemption itself is the mechanism, so the value-binding check is the only fix.\n\n#### Resources\n\n- [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.","state":0,"publishedAt":"2026-06-10T13:38:15+00:00","modifiedAt":"2026-09-10T03:50:55.2912383+00:00","affected":[{"ecosystem":"npm","name":"@hulumi/policies","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.4.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:L","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-9vc9-4jv3-rf86","https://github.com/kerberosmansour/hulumi/pull/175","https://github.com/kerberosmansour/hulumi/pull/178","https://github.com/kerberosmansour/hulumi"],"sourceUrl":"https://github.com/advisories/GHSA-9vc9-4jv3-rf86","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-9vc9-4jv3-rf86","identifiers":["GHSA-9vc9-4jv3-rf86","CVE-2026-48034"]},"retained":false,"historicalAffected":[]}],"coverage":[]}