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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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.

What is the EPSS score for GHSA-2ffm-hxrq-qqmm?

GHSA-2ffm-hxrq-qqmm has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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-2ffm-hxrq-qqmm?

GHSA-2ffm-hxrq-qqmm is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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 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-2ffm-hxrq-qqmm — @hulumi/drift

GHSA-2ffm-hxrq-qqmm is a CWE-345 vulnerability in @hulumi/drift. A fix is available for @hulumi/drift — see the affected versions and patch details below.

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

Also known asCVE-2026-82858

Published

May 21, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 2, 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-2ffm-hxrq-qqmm.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% 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/driftnpm

194downloads / 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`npm install @hulumi/drift@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works