CVE-2026-82856
Validation bypass in @hulumi/policies lets wildcard GitHub Actions OIDC subjects evade AWS policy checks
Is CVE-2026-82856 being exploited?
Not confirmed. CVE-2026-82856 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-82856?
CVE-2026-82856 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82856?
Yes. A fix has been recorded for CVE-2026-82856. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82856 affect?
CVE-2026-82856 affects @hulumi/policies < 1.3.2, GitHub Actions OIDC trust policies, AWS IAM role trust conditions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82856?
Upgrade to @hulumi/policies v1.3.2+, audit and tighten OIDC subject conditions
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Bypasses policy validation enabling attackers to hide ForAnyValue:StringLike subjects and assume AWS roles via GitHub Actions OIDC, leading to unauthorized AWS access and privilege escalation.
Immediate action required
- affected< 1.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.