dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-44679

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The forgot password flow in Tuist versions prior to 1.180.10 lacks server-side rate limiting, allowing unauthenticated attackers to repeatedly request password reset emails for any known account without restriction, enabling abuse of email delivery resources.

MitigationUpgrade to Tuist version 1.180.10 or later which implements rate limiting on the password reset endpoint; alternatively, add application-level throttling to limit password reset requests per IP or account.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Tuist CLI version
    Run 'tuist --version' in your terminal and note the output
    Affected if The version is lower than 1.180.10 (e.g., 1.180.0 through 1.180.9, or any version below 1.180.10)
  2. Determine if you use Tuist's cloud services
    Check whether your team uses Tuist Cloud (tuistcloud.com) or a self-hosted Tuist server instance for authentication
    Affected if You use Tuist Cloud or any self-hosted Tuist server for user authentication and the server version is below 1.180.10
  3. Inspect server configuration for rate limiting
    If self-hosting Tuist server, examine your server configuration files or deployment settings for any rate-limit, throttling, or request-throttling configuration related to password reset endpoints
    Affected if No rate limiting or throttling configuration exists for the '/forgot-password' or password reset endpoint
  4. Review server access logs for password reset abuse
    Check server access logs for repeated password reset requests, looking for multiple reset emails requested for different accounts from the same IP address within a short time window
    Affected if Logs show numerous password reset requests from a single source without apparent blocking or throttling

You are affected if your Tuist installation is below version 1.180.10 and you rely on Tuist's authentication services where the password reset endpoint lacks rate limiting.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Tuist version 1.180.10 or later which implements rate limiting on the password reset endpoint; alternatively, add application-level throttling to limit password reset requests per IP or account.

Recommended fix High confidence

1.180.10

  1. 1. Identify the current Tuist version in your deployment (e.g., check via `tuist --version` or your dependency manager)
  2. 2. If running a version prior to 1.180.10, upgrade to version 1.180.10 or later
  3. 3. For self-hosted deployments, verify the upgrade completed successfully by checking the installed version
  4. 4. Test the password reset flow to confirm rate limiting/throttling is now enforced
Caveat Review Tuist release notes for 1.180.10 to check for any breaking changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44679 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data