Authorization Flaw in Flow-Like (CVE-2026-50173)
Summary
Vulnerability in Flow-Like (CVE-2026-50173). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/apps/{app_id}/invoke/presign.
Original description
The description as published by the source.
Flow-Like is a platform for building end-to-end use cases. Prior to version 1.0.4, GET /api/v1/apps/{app_id}/invoke/presign grants Azure Blob Storage SAS credentials with write and delete access to app content to any app member that has ExecuteEvents, even when that member lacks ReadFiles and WriteFiles. The route treats file permissions as optional after the ExecuteEvents gate. When the caller has neither file permission, it selects CredentialsAccess::InvokeNone. In the Azure credential provider, InvokeNone still mints a content_sas_token for apps/{app_id} with sp=rwdl, plus user-content and log SAS tokens. The returned shared credential is enough for the low-privilege caller to directly write or delete blobs under the app content prefix. Version 1.0.4 patches the issue. Flow-Like Studio and the hosted Flow-Like Web App are not affected. These deployments use AWS-backed storage. Self-hosted deployments are only affected if they use Azure Blob Storage as the storage backend. In affected deployments, the issue only applies to authenticated app members who have workflow execution permissions but should not have app file write/delete permissions. Users of affected self-hosted Azure deployments should update to version 1.0.4 or the latest dev branch.
Source: NIST National Vulnerability Database NVD
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-50173 has been found in Flow-Like.
Attackers can target a specific entry point like GET /api/v1/apps/{app_id}/invoke/presign 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 "Flow-Like CVE-2026-50173" on the vendor's site.
CVE-2026-50173 (Flow-Like) — CWE-863
Attack surface: GET /api/v1/apps/{app_id}/invoke/presign / ExecuteEvents / ReadFiles / WriteFiles
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.
Incorrect authorization (CWE-863) exists in Flow-Like. Attackers reach the vulnerable code path via GET /api/v1/apps/{app_id}/invoke/presign.
Check the vendor advisory for the affected versions of Flow-Like. Attack surface: GET /api/v1/apps/{app_id}/invoke/presign / ExecuteEvents / ReadFiles / WriteFiles.
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 GET /api/v1/apps/{app_id}/invoke/presign requests with malformed payloads or SQL meta-characters. Run grep -r 'Flow-Like' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Flow-Like' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Flow-Likeを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/apps/{app_id}/invoke/presign' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/apps/{app_id}/invoke/presignへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/v1/apps/{app_id}/invoke/presign on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com