Improper Handling of Exceptional Conditions Affecting @hulumi/drift package, versions <1.4.0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-HULUMIDRIFT-17660548
- published27 Jun 2026
- disclosed10 Jun 2026
- creditkerberosmansour
Introduced: 10 Jun 2026
CVE-2026-48036 (opens in a new tab)How to fix?
Upgrade @hulumi/drift to version 1.4.0 or higher.
Overview
@hulumi/drift is a Local-first drift classifier and live posture validator — distinguishes provider-API churn from console break-glass from genuine IaC drift, then renders read-only live posture findings as JSON, Markdown, and SARIF. Verdict logic mirrors HulumiDrift.tla Ha
Affected versions of this package are vulnerable to Improper Handling of Exceptional Conditions due to improper handling of exceptional conditions in the classifier process. An attacker can cause legitimate drift detection results to be masked or false incident escalations to occur by triggering adapter failures or exploiting normal provider-API churn. This is only exploitable if the classifier is used in environments where verdicts are relied upon for incident workflows and adapter failures can occur.
Workaround
This vulnerability can be mitigated by setting the options.minConfidence: "medium" parameter on the classifier call, which prevents degraded verdicts from being cached, partially mitigating the risk of masking real attacks.