Vulnerability in @hulumi/baseline (CVE-2026-48035)
Summary
Vulnerability in @hulumi/baseline (CVE-2026-48035). Risk of unauthorized operations or information disclosure. Exploitable via AccountFoundation. Mitigation: upgrade to 1.4.0 or later.
Original description
The description as published by the source.
Hulumi is an open-source toolkit that ships secure-by-default cloud and platform infrastructure components for Pulumi. Prior to version 1.4.0, consumers using AccountFoundation could ship an AWS account whose CloudTrail / Config audit logs were deletable by any S3-delete-capable principal — while believing the startup-hardened tier guaranteed tamper-resistance. Sandbox-tier deployments had no audit immutability at all (defects 1 and 3 compounded). This issue has been patched in version 1.4.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48035 has been found in @hulumi/baseline.
Attackers can target a specific entry point like AccountFoundation over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @hulumi/baseline to 1.4.0 or later.
If unsure, ask your IT team or search "@hulumi/baseline CVE-2026-48035" on the vendor's site.
CVE-2026-48035 (@hulumi/baseline) — CWE-1059
Attack surface: AccountFoundation / forceDestroy / EventDataStore / SecureBucket
Patched: 1.4.0 — apply immediately
Workaround: Replicating audit logs out-of-account to an Object-Locked archive bucket partially mitigates while you upgrade.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1059) exists in @hulumi/baseline. Attackers reach the vulnerable code path via AccountFoundation.
Check the vendor advisory for the affected versions of @hulumi/baseline. Attack surface: AccountFoundation / forceDestroy / EventDataStore / SecureBucket.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.4.0.
Workaround: Replicating audit logs out-of-account to an Object-Locked archive bucket partially mitigates while you upgrade.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@hulumi/baseline' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@hulumi/baseline' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@hulumi/baselineを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Replicating audit logs out-of-account to an Object-Locked archive bucket partially mitigates while you upgrade.パッチが適用されるまでの応急処置として、Replicating audit logs out-of-account to an Object-Locked archive bucket partially mitigates while you upgrade. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @hulumi/baseline to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com