{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82857 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82857 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82857 is a critical vulnerability in kerberosmansour hulumi, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82857 and fix it if it is affected.\n\nWhat it is: CVE-2026-82857 is a critical vulnerability in kerberosmansour hulumi, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82857 in the wild and no public exploit code.\n\nAffected product: kerberosmansour hulumi. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-82857/ (Markdown: https://insights.sbomify.com/CVE-2026-82857/index.md)","id":"CVE-2026-82857","markdown":"https://insights.sbomify.com/CVE-2026-82857/index.md","name":"CVE-2026-82857","record":{"aliases":["GHSA-35qr-vx94-m5x3","GHSA-pjj3-j4q3-9wpg"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"hulumi IAM policy","requires_auth":"none","summary":"Attackers with specific principal access can create persistent higher-privilege roles in the sandbox account due to insufficient IAM policy boundaries.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"hulumi versions before v1.3.2 contain a privilege escalation vulnerability in the weekly integration IAM policy that allows role lifecycle operations on af-e2e-* roles without sufficient boundary restrictions. Attackers with the documented principal can create persistent higher-privilege roles in the sandbox account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"hulumi before v1.3.2 Privilege Escalation via IAM Policy","id":"CVE-2026-82857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"@hulumi/drift before 1.3.2 Unsafe Execute Plan Acceptance","id":"CVE-2026-82858"},"packages":[],"prev":{"headline":"@hulumi/policies before 1.3.2 OIDC Trust Policy Bypass","id":"CVE-2026-82856"},"products":["hulumi"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["kerberosmansour"]},"summary":"Attackers with specific principal access can create persistent higher-privilege roles in the sandbox account due to insufficient IAM policy boundaries.","url":"https://insights.sbomify.com/CVE-2026-82857/"}