Tuist is a virtual platform team for Swift app devs. In 1.180.8 and earlier, the DELETE…
Summary
Vulnerability reported (CVE-2026-44678). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id}.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44678 has been found.
Attackers can target a specific entry point like DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-44678" on the vendor's site.
CVE-2026-44678 — CWE-639
Attack surface: DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) has been reported. Attackers reach the vulnerable code path via DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id}.
Check the vendor advisory for the affected versions. Attack surface: DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id}.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Hunt for indicators of compromise detect
grep 'DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against DELETE /api/projects/{account_handle}/{project_handle}/previews/{preview_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov