GHSA-2ffm-hxrq-qqmm: @hulumi/drift Orphan Reconciler Accepted Externally Supplied Vulnerability

HIGH
Share
CWE-345
Published
Advisory Summary

GHSA-2ffm-hxrq-qqmm is a HIGH orphan reconciler accepted externally supplied vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting @hulumi/drift libraries in the npm ecosystem. The issue involves orphan reconciler accepted externally supplied execute plans. Remediation is available by upgrading affected packages to version 1.3.2.

GHSA-2ffm-hxrq-qqmm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2ffm-hxrq-qqmm
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product @hulumi/drift
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-2ffm-hxrq-qqmm

To remediate this vulnerability, upgrade all affected @hulumi/drift dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@hulumi/drift fixed: 1.3.2 
npm install @hulumi/drift@1.3.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @hulumi/drift

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-2ffm-hxrq-qqmm, inspect your project dependencies using npm:

npm ls @hulumi/drift

Analyze the terminal output to locate any version of @hulumi/drift in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.2), your application is affected.

Note: The npm ls @hulumi/drift command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In @hulumi/drift, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-2ffm-hxrq-qqmm Affected @hulumi/drift Versions

1 component(s)
Fixed Versions:
1.3.2
Product / Package Ecosystem Affected Versions Fixed Version
@hulumi/drift
npm/@hulumi/drift
npm
< 1.3.2
1.3.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-2ffm-hxrq-qqmm
@hulumi/drift Source Repository REPOSITORY
https://github.com/kerberosmansour/hulumi

Frequently Asked Questions

What is GHSA-2ffm-hxrq-qqmm?
GHSA-2ffm-hxrq-qqmm is a security vulnerability in @hulumi/drift involving Orphan reconciler accepted externally supplied execute plans under CWE-345: Insufficient Verification of Data Authenticity.
Which @hulumi/drift versions are affected?
Affected versions include releases prior to 1.3.2 across affected packages: @hulumi/drift.
What version fixes GHSA-2ffm-hxrq-qqmm?
Upgrading to 1.3.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @hulumi/drift affected?
Yes, @hulumi/drift is affected in releases prior to 1.3.2. Upgrade your dependency to 1.3.2 or later.
What CWE is associated with GHSA-2ffm-hxrq-qqmm?
GHSA-2ffm-hxrq-qqmm is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check npm dependencies for GHSA-2ffm-hxrq-qqmm?
Run the dependency tree command: 'npm ls @hulumi/drift'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2ffm-hxrq-qqmm",
  "modified" : "2026-05-21T20:43:41Z",
  "published" : "2026-05-21T20:43:41Z",
  "aliases" : [ ],
  "summary" : "@hulumi/drift: Orphan reconciler accepted externally supplied execute plans",
  "details" : "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.\n\nPatched in 1.3.2: execute-plan handling now validates provenance and rejects untrusted plans, with regression coverage.\n\nRemediation: upgrade @hulumi/drift to 1.3.2 or later.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@hulumi/drift"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-2ffm-hxrq-qqmm"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kerberosmansour/hulumi"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-21T20:43:41Z",
    "nvd_published_at" : null
  }
}