@hulumi/drift before 1.3.2 Unsafe Execute Plan Acceptance (CVE-2026-82858) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-82858

@hulumi/drift before 1.3.2 Unsafe Execute Plan Acceptance

Answer in brief

CVE-2026-82858 records a Unknown severity vulnerability in @hulumi/drift before 1.3.2 Unsafe Execute Plan Acceptance. The current sources do not mark it as known exploited. The current feed maps hulumi/drift (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 31, 2026Updated Aug 31, 2026Source checked Aug 31, 2026First seen by HOL Aug 31, 2026Material review Aug 31, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps hulumi/drift (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
hulumi/driftgeneric	>=0 <1.3.2	1.3.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for hulumi/drift.
Review the reported fix. Update hulumi/drift to 1.3.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 31, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.