Flow-Like: Azure invoke presign grants app content write SAS to ExecuteEvents-only users (CVE-2026-50173) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-50173

Flow-Like: Azure invoke presign grants app content write SAS to ExecuteEvents-only users

Answer in brief

CVE-2026-50173 records a Unknown severity vulnerability in Flow-Like: Azure invoke presign grants app content write SAS to ExecuteEvents-only users. The current sources do not mark it as known exploited. The current feed maps Rheosoph/flow-like (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Rheosoph/flow-like (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Rheosoph/flow-likegeneric	< 1.0.4	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Rheosoph/flow-like.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.