← Back
CLEANSTART-2026-QW08095
Vulnerability in pulumi (CLEANSTART-2026-QW08095)
Summary
vulnerability in pulumi (CLEANSTART-2026-QW08095). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `3.299.0-r0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CLEANSTART-2026-QW08095** has been found in pulumi.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade pulumi to **3.299.0-r0** or later.
If unsure, ask your IT team or search "pulumi CLEANSTART-2026-QW08095" on the vendor's site.
CLEANSTART-2026-QW08095 (pulumi) —
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.299.0-r0` — apply immediately
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.
❓ What is the problem
**A vulnerability** (unclassified) exists in pulumi.
📍 Affected scope
pulumi — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.299.0-r0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pulumi' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pulumi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pulumi` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pulumi to 3.299.0-r0ステージング環境で 3.299.0-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
CleanStart
pulumi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.299.0-r0"}]}]
References
- advisory https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-QW08095.json
- web https://osv.dev/vulnerability/CVE-2026-34040
- web https://osv.dev/vulnerability/CVE-2026-39883
- web https://osv.dev/vulnerability/ghsa-3xc5-wrhm-f963
- web https://osv.dev/vulnerability/ghsa-hfvc-g4fc-pqhx
- web https://osv.dev/vulnerability/ghsa-xmrv-pmrh-hhx2
- web https://nvd.nist.gov/vuln/detail/CVE-2026-34040
- web https://nvd.nist.gov/vuln/detail/CVE-2026-39883