Summary
@hulumi/policies: Stack-wide evidence bypassed Cloudflare and deployment-governance guardrails
Impact: @hulumi/policies versions before 1.3.2 used stack-wide evidence shortcuts in several Cloudflare and deployment-governance validators. Unrelated compliant-looking evidence could suppress violations for different zones, hostnames, origins, or repositories in the same stack.
Patched in 1.3.2: validators now correlate evidence to the specific protected resource and include regression coverage for unrelated-evidence bypasses.
Remediation: upgrade @hulumi/policies to 1.3.2 or later.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-59F3-7227-WMH4? GHSA-59F3-7227-WMH4 is a high-severity security vulnerability in @hulumi/policies (npm), affecting versions < 1.3.2. It is fixed in 1.3.2.
- Which versions of @hulumi/policies are affected by GHSA-59F3-7227-WMH4? @hulumi/policies (npm) versions < 1.3.2 is affected.
- Is there a fix for GHSA-59F3-7227-WMH4? Yes. GHSA-59F3-7227-WMH4 is fixed in 1.3.2. Upgrade to this version or later.
- Is GHSA-59F3-7227-WMH4 exploitable, and should I be worried? Whether GHSA-59F3-7227-WMH4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-59F3-7227-WMH4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-59F3-7227-WMH4? Upgrade
@hulumi/policiesto 1.3.2 or later.