Summary
@hulumi/baseline: AccountFoundation reuse paths silently downgrade GuardDuty / Security Hub posture
Affected: @hulumi/baseline < 1.4.0, Fixed in: 1.4.0, Severity: Medium, CWE-693 (Protection Mechanism Failure)
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.
- 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
guardDutyDetectorIdoutput as if the baseline were active. - Security Hub reuse. Although the account import was read-only, Hulumi unconditionally created the CIS / NIST
StandardsSubscriptionresources with default delete behaviour. Pulumi then treated those subscriptions as its own, a laterpulumi destroyof the stack would callBatchDisableStandards, unsubscribing the account from CIS / NIST compliance monitoring even on accounts that had those subscriptions before Hulumi ever ran.
Workarounds
Don't reuse pre-existing detective services with AccountFoundation before upgrading. If reuse is unavoidable, manually verify detector posture out-of-band.
Resources
- PR #178 (Cluster G); regression tests in
packages/baseline/tests/guardduty-reuse-posture.test.tsandpackages/baseline/tests/securityhub-reuse-retain.test.ts.
Impact
Consumers using AccountFoundation's reuse mode could:
- ship deployments that appeared to enable a detective baseline but actually weren't (case 1), or
- 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).
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to @hulumi/[email protected].
- GuardDuty reuse now asserts the imported detector is
ENABLEDwithfindingPublishingFrequency: FIFTEEN_MINUTES. Wrong posture fails the deploy at preview time. - Security Hub reuse creates the CIS / NIST
StandardsSubscriptionresources withretainOnDelete: true, so destroying a reused stack no longer unsubscribes the account.
Net-new (non-reuse) deployments are unchanged.
Frequently Asked Questions
- What is CVE-2026-48037? CVE-2026-48037 is a medium-severity security vulnerability in @hulumi/baseline (npm), affecting versions < 1.4.0. It is fixed in 1.4.0.
- Which versions of @hulumi/baseline are affected by CVE-2026-48037? @hulumi/baseline (npm) versions < 1.4.0 is affected.
- Is there a fix for CVE-2026-48037? Yes. CVE-2026-48037 is fixed in 1.4.0. Upgrade to this version or later.
- Is CVE-2026-48037 exploitable, and should I be worried? Whether CVE-2026-48037 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-48037 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-48037? Upgrade
@hulumi/baselineto 1.4.0 or later.