# CVE-2026-82862: Hulumi before v1.3.2 Helper Script Shadowing via Workspace Files

> Attackers can execute arbitrary code by placing malicious files in the workspace to shadow the intended helper script in Hulumi.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-ffgq-3pgp-p595, GHSA-mjcg-x5mr-27ww

## What is CVE-2026-82862?

CVE-2026-82862 is a high-severity path traversal vulnerability in kerberosmansour hulumi, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hulumi versions before v1.3.2 resolve the threat-model helper script from an unsafe root, allowing workspace files to shadow the intended helper script. Attackers can place malicious files in the workspace to execute arbitrary code during local skill execution.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2026-82862 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82862 is a high-severity path traversal vulnerability in kerberosmansour hulumi, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82862 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-82862/ (Markdown: https://insights.sbomify.com/CVE-2026-82862/index.md)
```

## Sources

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

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