{"answers":{"affected":"2 open source packages ship an affected version, including @hulumi/policies.","exploited":"There is no known exploitation of CVE-2026-82855 in the wild and no public exploit code.","fix":"Upgrade @hulumi/policies to 1.3.2 or later.","what":"CVE-2026-82855 is a critical vulnerability in hulumi policies, 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-82855 and fix it if it is affected.\n\nWhat it is: CVE-2026-82855 is a critical vulnerability in hulumi policies, 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-82855 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @hulumi/policies (npm): affected all versions; fixed in 1.3.2\n- @hulumi/policies (npm): affected all versions; fixed in 1.3.2\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-82855/ (Markdown: https://insights.sbomify.com/CVE-2026-82855/index.md)","id":"CVE-2026-82855","markdown":"https://insights.sbomify.com/CVE-2026-82855/index.md","name":"CVE-2026-82855","record":{"aliases":["GHSA-59f3-7227-wmh4","GHSA-8c24-v4pw-q2pm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Hulumi policies library","requires_auth":"none","summary":"Attackers can bypass security guardrails in Hulumi policies by submitting unrelated compliant evidence, allowing violations to be suppressed.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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-693","name":"Protection Mechanism Failure"}],"description":"@hulumi/policies versions before 1.3.2 contain an evidence validation bypass vulnerability in Cloudflare and deployment-governance validators that allows attackers to suppress violations by submitting unrelated compliant evidence. Attackers can use evidence from different zones, hostnames, origins, or repositories to bypass security guardrails for unrelated resources in the same stack.","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":false,"headline":"@hulumi/policies before 1.3.2 Evidence Validation Bypass","id":"CVE-2026-82855","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"@hulumi/policies before 1.3.2 OIDC Trust Policy Bypass","id":"CVE-2026-82856"},"packages":[{"ecosystem":"npm","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"@hulumi/policies","purl":null,"source":"GHSA-59f3-7227-wmh4"},{"ecosystem":"npm","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"@hulumi/policies","purl":"pkg:npm/%40hulumi/policies","source":"GHSA-59f3-7227-wmh4"}],"prev":{"headline":"Nodemailer before 8.0.4 SMTP Command Injection via envelope.size","id":"CVE-2026-82854"},"products":["policies"],"published":"2026-08-31","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":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["hulumi"]},"summary":"Attackers can bypass security guardrails in Hulumi policies by submitting unrelated compliant evidence, allowing violations to be suppressed.","url":"https://insights.sbomify.com/CVE-2026-82855/"}