Is CVE-2026-82856 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82856 being exploited in the wild.

How severe is CVE-2026-82856?

Critical severity, with a CVSS score of 9.8, published 31 August 2026.

Which products and versions are affected?

@hulumi/policies (npm) SEMVER:introduced=0,fixed=1.3.2.

Is there a fix for CVE-2026-82856?

Yes. @hulumi/policies (npm): upgrade to 1.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-82856 attacked?

It is attacked over the network.

Am I affected by CVE-2026-82856?

Check whether you run @hulumi/policies (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-82856: @hulumi/policies GitHub OIDC trust policy bypass via set-qualified condition operators

CVE-2026-82856 · Severity: critical · CVSS 9.8 · Published 2026-08-31

@hulumi/policies is a library that validates AWS IAM trust policies for security guardrails, particularly when using GitHub Actions OIDC authentication. Versions before 1.3.2 failed to properly inspect AWS set-qualified condition operators (like ForAnyValue:StringLike), allowing attackers to bypass critical security checks that prevent wildcard GitHub Actions subject claims in trust policies. This could allow unauthorized access to AWS resources when GitHub Actions workflows are misconfigured.

Technologies: @hulumi/policies (npm). Vendors: npm.

Quick answers

Is CVE-2026-82856 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82856 being exploited in the wild.
How severe is CVE-2026-82856?: Critical severity, with a CVSS score of 9.8, published 31 August 2026.
Which products and versions are affected?: @hulumi/policies (npm) SEMVER:introduced=0,fixed=1.3.2.
Is there a fix for CVE-2026-82856?: Yes. @hulumi/policies (npm): upgrade to 1.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82856 attacked?: It is attacked over the network.
Am I affected by CVE-2026-82856?: Check whether you run @hulumi/policies (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@hulumi/policies (npm): upgrade to 1.3.2 or later
```
npm install @hulumi/policies@1.3.2
```

Technical details

The vulnerability is an improper access control flaw (CWE-284) in the AWS trust-policy inspection logic. The vulnerable code in @hulumi/policies versions before 1.3.2 only validated AWS IAM condition operators when using exact StringLike/StringEquals keys in the G_OIDC_1 guardrail, but failed to evaluate set-qualified operators (prefixed with "ForAnyValue:" or similar). This allows an attacker to craft IAM trust policies with unsafe GitHub OIDC subject conditions that evade the mandatory validation. The attack requires the ability to define or modify AWS IAM trust policies. Patch 1.3.2 fixes this by properly evaluating all set-qualified string operators and rejecting unsafe GitHub OIDC sub conditions.

Affected products

hulumi @hulumi/policies < 1.3.2

Identifiers

CVE-2026-82856
GHSA-q2f7-m237-v562

Timeline

2026-05-21: disclosed: GitHub Security Advisory GHSA-q2f7-m237-v562 published
2026-05-21: patched: Version 1.3.2 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.