Is CVE-2026-48035 exploited in the wild?

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

How severe is CVE-2026-48035?

High 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-48035?

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-48035 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-48035?

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-48035: Hulumi AccountFoundation audit log deletion vulnerability

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

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-48035 attacked?

It is attacked with local access, in a software library.

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

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-48035 · Severity: high · CVSS 4 · Published 2026-07-24

The AccountFoundation component of @hulumi/baseline manages AWS audit logging infrastructure, which is critical for compliance, forensics, and detecting unauthorized activity. The vulnerability allows audit logs stored in S3 to be deleted by users with S3 delete permissions, destroying the forensic trail—while organizations believe their audit logging is tamper-proof. This puts compliance-sensitive deployments at risk of undetectable privilege abuse or data theft, and could enable attackers to cover their tracks after gaining access to an AWS account.

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

Quick answers

Is CVE-2026-48035 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48035 being exploited in the wild.
How severe is CVE-2026-48035?: High 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-48035?: 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-48035 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-48035?: 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

The vulnerability stems from CWE-1059 (Insufficient Technical Documentation / Behavioral Inconsistency) and comprises three independent weaknesses in how the AccountFoundation module configures S3 audit buckets: (1) the startup-hardened tier hard-coded objectLock: false despite intent to provide Write-Once-Read-Many (WORM) protection; (2) the forceDestroy flag was not restricted, allowing downstream stacks to set logBucketForceDestroy: true and purge all audit logs on Pulumi destruction; (3) sandbox-tier deployments skipped Object Lock, server access logging, and CloudTrail-Lake EventDataStore entirely, leaving no audit immutability. The fix in 1.4.0 enforces an invariant in SecureBucket that applies a deny-policy on s3:DeleteObject* for audit object prefixes, enables the CloudTrail-Lake EventDataStore regardless of tier, and blocks forceDestroy on startup-hardened buckets. The patch is available and users should upgrade immediately to prevent silent audit log deletion.

Affected products

@hulumi @hulumi/baseline < 1.4.0

Identifiers

CVE-2026-48035
GHSA-2mxr-p26x-mj73

Timeline

2026-06-10: disclosed: Advisory GHSA-2mxr-p26x-mj73 published
2026-05-19: patched: Patch merged in PR #178; version 1.4.0 released

References

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