# CVE-2026-82858: @hulumi/drift before 1.3.2 Unsafe Execute Plan Acceptance

> Attackers can supply malicious execute plans to bypass security checks and perform unsafe reconciliation operations in the Hulumi drift library.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-2ffm-hxrq-qqmm, GHSA-wpxp-22v5-r9cx

## What is CVE-2026-82858?

CVE-2026-82858 is a critical vulnerability in hulumi drift, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

@hulumi/drift versions before 1.3.2 accept externally supplied execute plans without sufficient provenance validation, allowing untrusted reconciliation input to be treated as trusted. Attackers can supply malicious execute plans that bypass security checks to perform unsafe reconciliation operations.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-82858?

2 open source packages ship an affected version, including @hulumi/drift.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@hulumi/drift` | npm | All versions | 1.3.2 |
| `@hulumi/drift` | npm | All versions | 1.3.2 |

## How do I fix CVE-2026-82858?

Upgrade @hulumi/drift to 1.3.2 or later.

## Is CVE-2026-82858 being exploited?

There is no known exploitation of CVE-2026-82858 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82858 and fix it if it is affected.

What it is: CVE-2026-82858 is a critical vulnerability in hulumi drift, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82858 in the wild and no public exploit code.

Affected packages and fixed versions:
- @hulumi/drift (npm): affected all versions; fixed in 1.3.2
- @hulumi/drift (npm): affected all versions; fixed in 1.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82858/ (Markdown: https://insights.sbomify.com/CVE-2026-82858/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82858
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82858
- OSV: https://osv.dev/vulnerability/CVE-2026-82858

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82858/
Summaries are generated and may contain mistakes; the official description above is the record.