# CVE-2026-82859: hulumi before v1.3.2 SCP Template Tag-on-Create Bypass

> Attackers can bypass IAM boundary restrictions in hulumi deployments by exploiting a weakened SCP template, allowing unauthorized resource creation.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-86q4-r5j3-ff5c, GHSA-qwm3-f9wh-qp63

## What is CVE-2026-82859?

CVE-2026-82859 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.

### Official description

hulumi versions before v1.3.2 contain a deployment SCP template that allows tag-on-create bypasses for hulumi:iac-role protections. Attackers can bypass intended IAM boundary restrictions by exploiting the weakened SCP template in downstream deployments.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-82859?


## How do I fix CVE-2026-82859?

No fix has been published for CVE-2026-82859 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82859 being exploited?

There is no known exploitation of CVE-2026-82859 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82859 and fix it if it is affected.

What it is: CVE-2026-82859 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.
Exploitation: There is no known exploitation of CVE-2026-82859 in the wild and no public exploit code.

Affected product: kerberosmansour hulumi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82859/ (Markdown: https://insights.sbomify.com/CVE-2026-82859/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82859
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82859
- OSV: https://osv.dev/vulnerability/CVE-2026-82859

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82859/
Summaries are generated and may contain mistakes; the official description above is the record.