{"answers":{"affected":"2 open source packages ship an affected version, including @hulumi/baseline.","exploited":"There is no known exploitation of CVE-2026-48035 in the wild and no public exploit code.","fix":"Upgrade @hulumi/baseline to 1.4.0 or later.","what":"CVE-2026-48035 is a high-severity vulnerability in kerberosmansour hulumi, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48035 and fix it if it is affected.\n\nWhat it is: CVE-2026-48035 is a high-severity vulnerability in kerberosmansour hulumi, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-48035 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @hulumi/baseline (npm): affected all versions; fixed in 1.4.0\n- @hulumi/baseline (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-48035/ (Markdown: https://insights.sbomify.com/CVE-2026-48035/index.md)","id":"CVE-2026-48035","markdown":"https://insights.sbomify.com/CVE-2026-48035/index.md","name":"CVE-2026-48035","record":{"aliases":["GHSA-2mxr-p26x-mj73"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Infrastructure as Code","requires_auth":"low_privilege","summary":"Attackers with S3 delete permissions can silently delete CloudTrail and Config audit logs, bypassing tamper-resistance guarantees in Hulumi AccountFoundation deployments.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1059","name":"Insufficient Technical Documentation"}],"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 using AccountFoundation could ship an AWS account whose CloudTrail / Config audit logs were deletable by any S3-delete-capable principal — while believing the startup-hardened tier guaranteed tamper-resistance. Sandbox-tier deployments had no audit immutability at all (defects 1 and 3 compounded). 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: AccountFoundation audit-delivery S3 bucket could be silently weakened","id":"CVE-2026-48035","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"misconfiguration","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Hulumi: Drift classifier fails open on adapter errors and over-promotes Mixed verdicts","id":"CVE-2026-48036"},"packages":[{"ecosystem":"npm","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"@hulumi/baseline","purl":null,"source":"GHSA-2mxr-p26x-mj73"},{"ecosystem":"npm","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"@hulumi/baseline","purl":"pkg:npm/%40hulumi/baseline","source":"GHSA-2mxr-p26x-mj73"}],"prev":{"headline":"HULUMI-H5 bypass via decoy sibling resources targeting a different bucket","id":"CVE-2026-48034"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-27","vendors":["kerberosmansour"]},"summary":"Attackers with S3 delete permissions can silently delete CloudTrail and Config audit logs, bypassing tamper-resistance guarantees in Hulumi AccountFoundation deployments.","url":"https://insights.sbomify.com/CVE-2026-48035/"}