CVE-2026-48036
Hulumi drift detection may mask real infra drift or falsely escalate churn.
Is CVE-2026-48036 being exploited?
Not confirmed. CVE-2026-48036 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-48036?
CVE-2026-48036 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48036?
Yes. A fix has been recorded for CVE-2026-48036. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48036 affect?
CVE-2026-48036 affects Hulumi < 1.4.0, Pulumi-based CI/cron drift-detection workflows, Infra-as-Code toolchains using Hulumi. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48036?
Upgrade Hulumi to >= 1.4.0 and validate drift workflows
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can have unauthorized infrastructure drift go undetected for up to 6 hours or trigger false incident escalations via adapter-result caching.
Patch when possible
- affected< 1.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.