How severe is GHSA-2ffm-hxrq-qqmm?

No CVSS score has been assigned to GHSA-2ffm-hxrq-qqmm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2ffm-hxrq-qqmm?

GHSA-2ffm-hxrq-qqmm affects the following packages: @hulumi/drift (npm). Ecosystems affected: npm.

How do I fix GHSA-2ffm-hxrq-qqmm?

Update @hulumi/drift to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ffm-hxrq-qqmm is resolved across your whole dependency graph.

How do I detect GHSA-2ffm-hxrq-qqmm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hulumi/drift. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2ffm-hxrq-qqmm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2ffm-hxrq-qqmm?

O3 pinpoints whether GHSA-2ffm-hxrq-qqmm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2ffm-hxrq-qqmm actively exploited in the wild?

No public exploit code has been indexed for GHSA-2ffm-hxrq-qqmm 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.

When was GHSA-2ffm-hxrq-qqmm published, and has it been updated?

GHSA-2ffm-hxrq-qqmm was published on May 21, 2026 and was last updated on May 21, 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-2ffm-hxrq-qqmm

GHSA-2ffm-hxrq-qqmm is a security vulnerability in @hulumi/drift. O3 Security confirms whether GHSA-2ffm-hxrq-qqmm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

@hulumi/drift: Orphan reconciler accepted externally supplied execute plans

Published

May 21, 2026

Updated

May 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 21, 2026 · OSV.dev, 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/driftnpm

558downloads / week

Description

Impact: @hulumi/drift versions before 1.3.2 could accept externally supplied execute plans without sufficient provenance checks, allowing unsafe reconciliation input to be treated as trusted.

Patched in 1.3.2: execute-plan handling now validates provenance and rejects untrusted plans, with regression coverage.

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hulumi/drift`	all versions	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/drift. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @hulumi/drift to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ffm-hxrq-qqmm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2ffm-hxrq-qqmm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2ffm-hxrq-qqmm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Impact: @hulumi/drift versions before 1.3.2 could accept externally supplied execute plans without sufficient provenance checks, allowing unsafe reconciliation input to be treated as trusted. Patched in 1.3.2: execute-plan handling now validates provenance and rejects untrusted plans, with regression coverage. Remediation: upgrade @hulumi/drift to 1.3.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-2ffm-hxrq-qqmm in your dependencies?

O3 detects GHSA-2ffm-hxrq-qqmm across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works