EUVD-2026-68448
GHSA-9pm9-rvf2-mhqv
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthor admin-equivalent IAM policy
-
DeliveryShape it as unhandled inline/attached evidence
-
ExploitSubmit to @hulumi/policies guardrail
-
ExecutionValidator skips inspection, marks compliant
-
PersistOver-privileged policy deployed
-
ImpactUndetected admin-equivalent access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that @hulumi/policies (version < 1.3.2) is used as the enforcement/detection mechanism for the administrator-policy guardrail (CIS 1.16), and that the attacker can introduce or influence an IAM policy - specifically an inline or attached policy crafted into an admin-equivalent shape not fully inspected by the validator. The limiting factor is that the flaw only matters where this library gates policy approval; it does not itself grant access but allows an admin-equivalent policy to evade detection. The concrete condition is the presence of unhandled inline/attached IAM policy evidence paths that the pre-1.3.2 validator skipped. |
| Impact | The CVSS 4.0 base score is 9.3 (Critical) with vector AV:N/AC:L/AT:N/PR:N/UI:N and high confidentiality, integrity, and availability impact to the vulnerable system (VC:H/VI:H/VA:H), no scope change to subsequent systems. That said, the realistic risk is nuanced: this is a control-bypass/detection-evasion weakness in a compliance-validation library rather than a direct remote-code-execution or direct-access primitive. The tangible impact is that an over-privileged IAM policy passes as compliant, so the '9.3' should be read as the downstream consequence (undetected admin-equivalent access) rather than a one-shot remote takeover. There is no EPSS score, no KEV listing, and no POC in the provided data, so exploitation appears theoretical/undemonstrated so far; teams that depend on @hulumi/policies as a gating check in CI/CD or cloud-governance pipelines should nonetheless prioritize upgrading, since a bypassed guardrail can mask serious IAM misconfigurations. Where this library is not in the enforcement path, the practical urgency is lower. |
| Exploit ScenarioDerived | An attacker or insider with the ability to author IAM policies crafts an admin-equivalent inline or attached policy in a shape the pre-1.3.2 validator does not fully inspect. The governance pipeline using @hulumi/policies evaluates it as compliant with the CIS 1.16 administrator-policy guardrail, so the over-privileged grant is deployed and persists undetected. No public exploit code is currently identified, but the bypass requires only knowledge of the unhandled policy shape. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAI
Privilege escalation in the @hulumi/policies npm package before 1.3.2 lets attackers bypass the administrator-policy guardrail (CIS 1.16) by crafting admin-equivalent inline or attached IAM policy shapes that the validator failed to fully inspect. Any environment relying on this library to detect over-privileged IAM policies could silently pass admin-equivalent access as compliant. No public exploit has been identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
Vendor-released patch: upgrade @hulumi/policies to 1.3.2 or later, which extends the validator to inspect the previously missed inline and attached IAM policy shapes and adds regression tests. Update the dependency in package.json/lockfiles and re-run your policy evaluation across existing IAM inventory, since any admin-equivalent policies that previously passed may now be correctly flagged and require remediation. If you cannot upgrade immediately, compensating controls include adding an independent secondary check for admin-equivalent IAM policies (for example a separate scan for wildcard '*:*' action/resource grants in both inline and attached policies) so the guardrail is not a single point of failure, and treating current @hulumi/policies 'pass' results as unverified until re-scanned - the trade-off is added pipeline time and potential duplicate findings. See GHSA-4xrh-5m3m-328w and the VulnCheck advisory for details.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in npm, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
@hulumi/policies is a Node.js/npm policy-validation library used to enforce IAM guardrails - here specifically the CIS Benchmark 1.16 control that flags IAM policies granting full administrative privileges. The root cause maps to CWE-269 (Improper Privilege Management): the pre-1.3.2 validator did not fully inspect every representation of policy evidence, evaluating some inline and attached IAM policy shapes incompletely. Because certain admin-equivalent policy paths were never examined, a policy that effectively grants '*:*' or equivalent could evade the guardrail. The CPE cpe:2.3:a:hulumi:policies:*:*:*:*:*:*:*:* identifies the affected component; the fix in 1.3.2 broadened the inspected policy shapes and added regression tests.
Know when Hulumi gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Bypass requires the ability to author/submit an IAM policy (PR:L) and undermines integrity of the guardrail decision (I:H); it does not directly disclose data (C:N) or affect availability (A:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
@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.
Technical POC Analysis
The bug class is CWE-269, Improper Privilege Management, in the npm package @hulumi/policies before 1.3.2.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Evidence-validation bypass in @hulumi/policies (npm) before 1.3.2 lets actors in a deployment pipeline suppress Cloudfla
IAM boundary bypass in hulumi versions before v1.3.2 stems from a deployment Service Control Policy (SCP) template that
Privilege escalation in hulumi before v1.3.2 lets an actor holding the documented IAM principal abuse the weekly integra
Security-guardrail bypass in the @hulumi/policies npm library (versions before 1.3.2) allows dangerous AWS IAM configura
Security-check bypass in @hulumi/drift before 1.3.2 allows remote attackers to submit forged execute plans that the orph
Policy evaluation bypass in @hulumi/policies before 1.3.2 permits unauthenticated remote attackers to submit forged Secu
Incomplete CloudTrail event-selector tampering detection in @hulumi/baseline before 1.3.2 (CWE-778: Insufficient Logging
Arbitrary code execution in Hulumi before v1.3.2 is possible through a CWE-426 untrusted search path flaw in the threat-
Exploit-DB