@hulumi/policies versions before 1.3.2 fail to fully inspect inline and attached IAM policy evidence for the administrator-policy guardrail. Attackers can craft admin-equivalent policy paths that bypass policy evaluation controls.
CVE-2026-82860
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-31. the CNA's CVSS baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 31, 2026
Last Modified
August 31, 2026
Advisory Details (2)
Auto-updated Aug 31, 2026@hulumi/policies before 1.3.2 Admin Policy Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/hulumi-policies-before-1.3.2-admin-policy-bypassCIS 1.16 admin policy bypass for inline and attached IAM policies · Advisory · kerberosmansour/hulumi · GitHub
Affected: 1.3.2: the validator inspects the affected policy shapes and includes regression
https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-4xrh-5m3m-328wVendor Advisories for CVE-2026-82860(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-31 14:45 UTCEG score recompute
- 2026-08-31 14:45 UTCGHSA enrichment
- 2026-08-31 13:37 UTCGHSA enrichment
- 2026-08-31 09:37 UTCEG score recompute
- 2026-08-31 09:37 UTCGHSA enrichment
- 2026-08-31 08:55 UTCEG score recompute
- 2026-08-31 08:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(4)
What is CVE-2026-82860?
When was CVE-2026-82860 disclosed?
What is the CVSS score of CVE-2026-82860?
How do I remediate CVE-2026-82860?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82860
Is Your Infrastructure Affected by CVE-2026-82860?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.