@hulumi/policies before 1.3.2 OIDC Trust Policy Bypass (CVE-2026-82856) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-82856

@hulumi/policies before 1.3.2 OIDC Trust Policy Bypass

Answer in brief

CVE-2026-82856 records a Unknown severity vulnerability in @hulumi/policies before 1.3.2 OIDC Trust Policy Bypass. The current sources do not mark it as known exploited. The current feed maps hulumi/policies (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/policies (generic). Check affected ranges and fixed versions before updating.

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

Recommended response

Check inventory. Check lockfiles and deployed manifests for hulumi/policies.
Review the reported fix. Update hulumi/policies 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/policies versions before 1.3.2 fail to properly validate set-qualified AWS IAM condition operators in GitHub OIDC trust policies. Attackers can use ForAnyValue:StringLike operators to hide wildcard GitHub Actions OIDC subject conditions from security guardrails.

Quoted source text, attributed separately from HOL analysis.