Vulnerability in @hulumi/drift (CVE-2026-48036)
Summary
Vulnerability in @hulumi/drift (CVE-2026-48036). Risk of unauthorized operations or information disclosure. Exploitable via Mixed. 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 running drift detection in CI / cron could see transient adapter failures silently cached as "all clear" — masking real attacks for up to six hours — or see ordinary provider-version churn falsely promoted to incident severity. Either way, the verdict source was unreliable for downstream incident workflows that gate on it. 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-48036 has been found in @hulumi/drift.
Attackers can target a specific entry point like Mixed over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @hulumi/drift to 1.4.0 or later.
If unsure, ask your IT team or search "@hulumi/drift CVE-2026-48036" on the vendor's site.
CVE-2026-48036 (@hulumi/drift) — CWE-755
Attack surface: Mixed / ConsoleBreakGlass
Patched: 1.4.0 — apply immediately
Workaround: Setting options.minConfidence: "medium" on the classifier call prevents the degraded None / none from being cached (it doesn't meet the threshold), partially mitigating case (1).
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-755) exists in @hulumi/drift. Attackers reach the vulnerable code path via Mixed.
Check the vendor advisory for the affected versions of @hulumi/drift. Attack surface: Mixed / ConsoleBreakGlass.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.4.0.
Workaround: Setting options.minConfidence: "medium" on the classifier call prevents the degraded None / none from being cached (it doesn't meet the threshold), partially mitigating case (1).
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@hulumi/drift' . 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/drift' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@hulumi/driftを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Setting `options.minConfidence: "medium"` on the classifier call prevents the degraded `None / none` from being cached (it doesn't meet the threshold), partially mitigating case (1).パッチが適用されるまでの応急処置として、Setting
options.minConfidence: "medium"on the classifier call prevents the degradedNone / nonefrom being cached (it doesn't meet the threshold), partially mitigating case (1). を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade @hulumi/drift 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