dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-44678

HIGH · 7.1 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 →
77/100
Remediation priority · High
Remotely reachable 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. 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.

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 DELETE endpoint for previews authorizes the caller against the project specified in the URL path (account_handle/project_handle), but then loads the preview solely by its UUID without verifying that the preview actually belongs to that project. An attacker can delete any preview in the system by providing its UUID while being authorized against a different project they control.

MitigationAdd a check verifying that the preview's project_id matches the project resolved from the URL path before performing the delete operation.

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
Low
Authentication
X
User interaction
None
Scope
X

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/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. Identify the product and version
    Locate the application software and determine its installed version through package manifests, binary metadata, or the application's version endpoint if available
    Affected if The installed version matches any vulnerable release of the software that contains the preview DELETE endpoint
  2. Locate the preview deletion endpoint handler
    Search the codebase for the DELETE route handler that processes requests to /previews/{preview_uuid} or similar path patterns for preview deletion
    Affected if The endpoint exists and processes DELETE requests for previews by UUID
  3. Examine authorization logic in the delete handler
    Review the delete handler code to identify where project authorization occurs and whether preview.project_id is validated against the URL-path-resolved project before deletion
    Affected if The code performs project authorization but does NOT validate that preview.project_id matches the project from the URL path before executing the delete
  4. Verify UUID-based preview loading without ownership check
    Check if the preview is loaded solely by UUID parameter and the delete proceeds without cross-referencing the preview's owning project with the authorized project from the request
    Affected if The preview is loaded and deleted using only its UUID without verifying project ownership
  5. Test for IDOR vulnerability
    If possible, issue a DELETE request for a preview UUID from a project you are authorized to access, but reference a preview UUID that belongs to a different project
    Affected if The delete operation succeeds for a preview that belongs to a different project than the one authorized in the URL path

The environment is affected if the preview deletion endpoint exists and performs authorization against the URL project but fails to verify that the preview's project_id matches that authorized project before deletion.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a check verifying that the preview's project_id matches the project resolved from the URL path before performing the delete operation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44678 — 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-44678 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