Hulumi is an open-source toolkit that ships secure-by-default cloud and platform infrastructure components for Pulumi. Prior to version 1.4.0, policy packs can be bypassed by a forged Pulumi-URN logical name. This issue has been patched in version 1.4.0.
CVE-2026-48033
This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(medium)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity84% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
July 24, 2026
Advisory Details (3)
Auto-updated Jul 24, 2026Policy packs bypassed by a forged Pulumi-URN logical name · Advisory · kerberosmansour/hulumi · GitHub
https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-rhgj-6g2c-frmmv1.4.0
Patch available: kerberosmansour/hulumi v1.4.0
https://github.com/kerberosmansour/hulumi/releases/tag/v1.4.0security: 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/178Vendor Advisories for CVE-2026-48033(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @hulumi/policies | — | 1.4.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-07-26 21:04 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 05:19 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 19:08 UTCEG score recompute▲ 8.40
- 2026-07-24 19:06 UTCMITRE cvelistV5CVSS v3 → 8.4 · CVSS v4 → 8.4
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-10 14:17 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS p91CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS p99CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8CRITICAL
- CVE-2020-10887EG 9.8EPSS p90CRITICAL
- CVE-2017-3197EG 9.8EPSS p92CRITICAL
- CVE-2018-9318EG 9.8EPSS p90CRITICAL
- CVE-2018-9311EG 9.8EPSS p90CRITICAL
- CVE-2017-8864EG 9.8CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS p100CRITICAL
Frequently asked(5)
What is CVE-2026-48033?
When was CVE-2026-48033 disclosed?
Is CVE-2026-48033 actively exploited?
What is the CVSS score of CVE-2026-48033?
How do I remediate CVE-2026-48033?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48033
Is Your Infrastructure Affected by CVE-2026-48033?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.