# CVE-2026-44678: Tuist: IDOR in preview deletion API allows cross-tenant deletion of any preview by UUID

> Attackers can delete previews from other tenants by supplying arbitrary UUIDs, bypassing project-level authorization checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 16 May 2026
- **Also known as:** GHSA-fqp5-hg46-cp2x

## What is CVE-2026-44678?

CVE-2026-44678 is a high-severity missing authorization vulnerability in tuist, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tuist is a virtual platform team for Swift app devs. In 1.180.8 and earlier, the DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id} endpoint loads the preview by its UUID without verifying that the preview belongs to the project resolved from the URL path. The route's project-level authorization plug (AuthorizationPlug, :preview) authorizes the caller against the project encoded in account_handle/project_handle — which the attacker controls — and then the action deletes whichever preview's UUID is supplied. The check therefore guards the wrong project.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-44678 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44678 is a high-severity missing authorization vulnerability in tuist, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44678 in the wild and no public exploit code.

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

## Sources

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

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