{"id":"CVE-2026-48037","aliases":["GHSA-cj8g-prcm-mfg5"],"title":"@hulumi/baseline: AccountFoundation reuse paths silently downgrade GuardDuty / Security Hub posture","summary":"@hulumi/baseline: AccountFoundation reuse paths silently downgrade GuardDuty / Security Hub posture","severity":"medium","cwe":["CWE-693"],"vendor":"hulumi","product":"@hulumi/baseline","ecosystem":"npm","affected":["@hulumi/baseline < 1.4.0"],"patched":["@hulumi/baseline 1.4.0"],"published":"2026-06-10","updated":"2026-06-10","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-cj8g-prcm-mfg5","references":[{"url":"https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-cj8g-prcm-mfg5"},{"url":"https://github.com/kerberosmansour/hulumi/pull/178"},{"url":"https://github.com/advisories/GHSA-cj8g-prcm-mfg5"}],"tags":["ghsa","npm"],"ingestedAt":"2026-07-07T15:41:59.572Z","epss":0.0026,"epssPercentile":0.18,"slug":"CVE-2026-48037","body":"## Overview\n\n**Affected:** `@hulumi/baseline` `< 1.4.0` — **Fixed in:** `1.4.0` — **Severity:** Medium — **CWE-693 (Protection Mechanism Failure)**\n\n#### Summary\n\n`AccountFoundation` can either create AWS detective services (GuardDuty for threat detection, Security Hub for compliance dashboards) or reuse pre-existing ones via opt-in flags. The reuse paths just imported the existing resources and reported success — they never checked whether the existing services were actually doing their job.\n\n1. **GuardDuty reuse.** If the existing detector was suspended, or set to the slower 6-hour publishing cadence instead of the baseline 15-minute one, or otherwise misconfigured — Hulumi never noticed. The deployment succeeded with a misleadingly-positive `guardDutyDetectorId` output as if the baseline were active.\n2. **Security Hub reuse.** Although the account import was read-only, Hulumi unconditionally created the CIS / NIST `StandardsSubscription` resources with default delete behaviour. Pulumi then treated those subscriptions as its own — a later `pulumi destroy` of the stack would call `BatchDisableStandards`, unsubscribing the account from CIS / NIST compliance monitoring even on accounts that had those subscriptions before Hulumi ever ran.\n\n#### Impact\n\nConsumers using `AccountFoundation`'s reuse mode could:\n\n- ship deployments that appeared to enable a detective baseline but actually weren't (case 1), or\n- accidentally turn off CIS / NIST compliance monitoring on an existing account just by destroying a Hulumi stack (case 2 — no malicious intent needed; a normal stack teardown was enough).\n\n#### Patches\n\nUpgrade to `@hulumi/baseline@1.4.0`.\n\n- GuardDuty reuse now asserts the imported detector is `ENABLED` with `findingPublishingFrequency: FIFTEEN_MINUTES`. Wrong posture fails the deploy at preview time.\n- Security Hub reuse creates the CIS / NIST `StandardsSubscription` resources with `retainOnDelete: true`, so destroying a reused stack no longer unsubscribes the account.\n\nNet-new (non-reuse) deployments are unchanged.\n\n#### Workarounds\n\nDon't reuse pre-existing detective services with `AccountFoundation` before upgrading. If reuse is unavoidable, manually verify detector posture out-of-band.\n\n#### Resources\n\n- [PR #178](https://github.com/kerberosmansour/hulumi/pull/178) (Cluster G); regression tests in\n  `packages/baseline/tests/guardduty-reuse-posture.test.ts` and\n  `packages/baseline/tests/securityhub-reuse-retain.test.ts`.\n\n## Affected packages\n\n- `@hulumi/baseline < 1.4.0`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `@hulumi/baseline 1.4.0`","depth":"sunlit","depthScore":28,"depthScoreParts":{"impact":27.5,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}