CVE-2026-48036

HIGHPre-NVD 8.48.4
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Hulumi is an open-source toolkit that ships secure-by-default cloud and platform infrastructure components for Pulumi. Prior to version 1.4.0, consumers running drift detection in CI / cron could see transient adapter failures silently cached as "all clear" — masking real attacks for up to six hours — or see ordinary provider-version churn falsely promoted to incident severity. Either way, the verdict source was unreliable for downstream incident workflows that gate on it. This issue has been patched in version 1.4.0.

CVSS v3
8.4
EG Score
8.4(low)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
12.5%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated Jul 24, 2026
Patch available. Sources: github, github_pr, github_release.
github Patch Available

Drift classifier fails open on adapter errors and over-promotes Mixed verdicts · Advisory · kerberosmansour/hulumi · GitHub

https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-32g3-35g9-wc9g
github_release Patch Available

v1.4.0

Patch available: kerberosmansour/hulumi v1.4.0

https://github.com/kerberosmansour/hulumi/releases/tag/v1.4.0
github_pr Patch Available

security: fix 4 HIGH + 15 MEDIUM Codex findings (8 root-cause clusters) — DCO-signed replacement for #177

Patch available: kerberosmansour/hulumi v1.4.0 (PR #178 merged 2026-05-19)

https://github.com/kerberosmansour/hulumi/pull/178

Vendor Advisories for CVE-2026-48036(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@hulumi/drift1.4.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 19:07 UTCEG score recompute 8.40
  2. 2026-07-24 19:06 UTCMITRE cvelistV5CVSS v3 → 8.4 · CVSS v4 → 8.4
  3. 2026-07-23 03:18 UTCEG score recompute
  4. 2026-06-14 23:18 UTCEPSS rescore
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-12 23:12 UTCEPSS rescore
  7. 2026-06-10 14:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48036?
CVE-2026-48036 is a high vulnerability published on June 10, 2026. Hulumi is an open-source toolkit that ships secure-by-default cloud and platform infrastructure components for Pulumi. Prior to version 1.4.0, consumers running drift detection in CI / cron could see transient adapter failures silently cached as "all clear" — masking real attacks for up to six…
When was CVE-2026-48036 disclosed?
CVE-2026-48036 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48036 actively exploited?
CVE-2026-48036 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48036?
CVE-2026-48036 has a CVSS v3 base score of 8.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48036?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48036, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48036

Explore →

Is Your Infrastructure Affected by CVE-2026-48036?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.