# CVE-2026-44679: Tuist: Forgot password flow lacks throttling for reset email delivery

> Unauthenticated attackers can spam password reset emails in Tuist, causing resource exhaustion and denial of service in self-hosted deployments.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-v7gr-7ww5-w4cx

## What is CVE-2026-44679?

CVE-2026-44679 is a medium-severity denial of service vulnerability in tuist, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tuist is a virtual platform team for Swift app devs. Prior to 1.180.10, the forgot password flow allows an unauthenticated attacker to repeatedly trigger password reset emails for a known account without server-side throttling. In self-hosted deployments, this can be abused to send large volumes of unwanted email and consume downstream email delivery resources. This vulnerability is fixed in 1.180.10.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-44679 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44679 is a medium-severity denial of service vulnerability in tuist, published on 14 May 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-44679 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-44679/ (Markdown: https://insights.sbomify.com/CVE-2026-44679/index.md)
```

## Sources

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

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