# CVE-2026-75038: Predictable temporary file in /tmp allows symlink attack in LACT

> Local attackers can exploit predictable temporary files to perform symlink attacks, causing denial of service in LACT.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-gcmx-rfrg-443v

## What is CVE-2026-75038?

CVE-2026-75038 is a medium-severity path traversal vulnerability in ilya-zlobintsev LACT, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

UNIX symbolic link (symlink) following vulnerability in ilya-zlobintsev/LACT allows for local denial-of-service. This issue affects LACT: through 0.10.0.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

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


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

Upgrade to a fixed version.

## Is CVE-2026-75038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75038 is a medium-severity path traversal vulnerability in ilya-zlobintsev LACT, published on 25 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-75038 in the wild and no public exploit code.

Affected product: ilya-zlobintsev LACT. 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-75038/ (Markdown: https://insights.sbomify.com/CVE-2026-75038/index.md)
```

## Sources

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

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