How severe is GHSA-4xrh-5m3m-328w?

No CVSS score has been assigned to GHSA-4xrh-5m3m-328w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4xrh-5m3m-328w?

GHSA-4xrh-5m3m-328w affects the following packages: @hulumi/policies (npm). Ecosystems affected: npm.

How do I fix GHSA-4xrh-5m3m-328w?

Update @hulumi/policies to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xrh-5m3m-328w is resolved across your whole dependency graph.

How do I detect GHSA-4xrh-5m3m-328w in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hulumi/policies, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4xrh-5m3m-328w if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-4xrh-5m3m-328w actively exploited in the wild?

No public exploit code has been indexed for GHSA-4xrh-5m3m-328w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4xrh-5m3m-328w?

GHSA-4xrh-5m3m-328w has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4xrh-5m3m-328w?

GHSA-4xrh-5m3m-328w is classified as Improper Privilege Management (CWE-269). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4xrh-5m3m-328w published, and has it been updated?

GHSA-4xrh-5m3m-328w was published on May 21, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-4xrh-5m3m-328w — @hulumi/policies

GHSA-4xrh-5m3m-328w is a Improper Privilege Management vulnerability in @hulumi/policies. A fix is available for @hulumi/policies — see the affected versions and patch details below.

@hulumi/policies: CIS 1.16 admin policy bypass for inline and attached IAM policies

Also known asCVE-2026-82860

Published

May 21, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4xrh-5m3m-328w.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.24%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@hulumi/policiesnpm

262downloads / week

Description

Patched in 1.3.2: the validator inspects the affected policy shapes and includes regression tests.

Remediation: upgrade @hulumi/policies to 1.3.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hulumi/policies`	all versions	1.3.2`npm install @hulumi/policies@1.3.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hulumi/policies, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @hulumi/policies to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xrh-5m3m-328w is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

Impact: @hulumi/policies versions before 1.3.2 did not fully inspect inline and attached IAM policy evidence for the administrator-policy guardrail, so some admin-equivalent policy paths could pass policy evaluation. Patched in 1.3.2: the validator inspects the affected policy shapes and includes regression tests. Remediation: upgrade @hulumi/policies to 1.3.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-4xrh-5m3m-328w in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works