Is CVE-2026-48037 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48037 being exploited in the wild.

How severe is CVE-2026-48037?

Medium severity, with a CVSS score of 4, published 24 July 2026.

Which products and versions are affected?

@hulumi/baseline (npm) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0.

Is there a fix for CVE-2026-48037?

Yes. @hulumi/baseline (npm): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48037 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48037?

Check whether you run @hulumi/baseline (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48037: Hulumi security posture downgrade in AccountFoundation reuse paths

Q: Is there a fix for CVE-2026-48037?

Yes. @hulumi/baseline (npm): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48037 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-48037?

Check whether you run @hulumi/baseline (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48037 · Severity: medium · CVSS 4 · Published 2026-07-24

Hulumi, a toolkit for deploying secure cloud infrastructure, contains a flaw in how it handles existing AWS security services. When configured to reuse existing GuardDuty or Security Hub setups, the software may fail to verify that security monitoring is actually active or may accidentally disable compliance monitoring during a routine system teardown. This can lead to a false sense of security where critical threat detection and compliance alerts are silently disabled or misconfigured.

Technologies: @hulumi/baseline (npm). Vendors: npm.

Quick answers

Is CVE-2026-48037 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48037 being exploited in the wild.
How severe is CVE-2026-48037?: Medium severity, with a CVSS score of 4, published 24 July 2026.
Which products and versions are affected?: @hulumi/baseline (npm) < 1.4.0, SEMVER:introduced=0,fixed=1.4.0.
Is there a fix for CVE-2026-48037?: Yes. @hulumi/baseline (npm): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48037 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48037?: Check whether you run @hulumi/baseline (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@hulumi/baseline (npm): upgrade to 1.4.0 or later
```
npm install @hulumi/baseline@1.4.0
```

Technical details

A protection mechanism failure (CWE-693) exists in the @hulumi/baseline package when using AccountFoundation's resource reuse paths. The toolkit failed to validate the operational state of imported GuardDuty detectors, allowing deployments to succeed even if threat detection was suspended or set to sub-optimal publishing frequencies. Additionally, Security Hub reuse paths lacked proper resource retention logic; a 'pulumi destroy' operation would trigger BatchDisableStandards, unintentionally unsubscribing the account from CIS/NIST compliance standards. Version 1.4.0 addresses these issues by asserting detector status at preview time and implementing 'retainOnDelete' for Security Hub subscriptions.

Affected products

kerberosmansour @hulumi/baseline < 1.4.0

Identifiers

CVE-2026-48037
GHSA-cj8g-prcm-mfg5

Timeline

2026-05-19: other: Fixes merged in pull request 178
2026-05-20: patched: Version 1.4.0 released
2026-07-24: disclosed: CVE published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.