{"answers":{"affected":"2 open source packages ship an affected version, including @hulumi/drift.","exploited":"There is no known exploitation of CVE-2026-48036 in the wild and no public exploit code.","fix":"Upgrade @hulumi/drift to 1.4.0 or later.","what":"CVE-2026-48036 is a high-severity vulnerability in kerberosmansour hulumi, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48036 and fix it if it is affected.\n\nWhat it is: CVE-2026-48036 is a high-severity vulnerability in kerberosmansour hulumi, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-48036 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @hulumi/drift (npm): affected all versions; fixed in 1.4.0\n- @hulumi/drift (npm): affected all versions; fixed in 1.4.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48036/ (Markdown: https://insights.sbomify.com/CVE-2026-48036/index.md)","id":"CVE-2026-48036","markdown":"https://insights.sbomify.com/CVE-2026-48036/index.md","name":"CVE-2026-48036","record":{"aliases":["GHSA-32g3-35g9-wc9g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Infrastructure security toolkit","requires_auth":"none","summary":"Attackers can mask real infrastructure attacks or trigger false incidents by exploiting drift classifier failures in Hulumi, undermining security monitoring reliability.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Hulumi: Drift classifier fails open on adapter errors and over-promotes Mixed verdicts","id":"CVE-2026-48036","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Hulumi: AccountFoundation reuse paths silently downgrade GuardDuty / Security Hub posture","id":"CVE-2026-48037"},"packages":[{"ecosystem":"npm","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"@hulumi/drift","purl":null,"source":"GHSA-32g3-35g9-wc9g"},{"ecosystem":"npm","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"@hulumi/drift","purl":"pkg:npm/%40hulumi/drift","source":"GHSA-32g3-35g9-wc9g"}],"prev":{"headline":"Hulumi: AccountFoundation audit-delivery S3 bucket could be silently weakened","id":"CVE-2026-48035"},"products":["hulumi"],"published":"2026-07-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-25","vendors":["kerberosmansour"]},"summary":"Attackers can mask real infrastructure attacks or trigger false incidents by exploiting drift classifier failures in Hulumi, undermining security monitoring reliability.","url":"https://insights.sbomify.com/CVE-2026-48036/"}