CVE-2026-50173: CWE-863: Incorrect Authorization in Rheosoph flow-like
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.
AI Analysis
Technical Summary
In Rheosoph flow-like versions before 1.0.4, the API endpoint GET /api/v1/apps/{app_id}/invoke/presign grants Azure Blob Storage SAS credentials with write and delete permissions to any app member possessing the ExecuteEvents permission, even if they lack ReadFiles and WriteFiles permissions. The endpoint incorrectly treats file permissions as optional after verifying ExecuteEvents, resulting in the Azure credential provider issuing a content SAS token with sp=rwdl (read, write, delete, list) privileges. This allows low-privilege authenticated users to write or delete blobs under the app content prefix. The vulnerability is limited to self-hosted deployments using Azure Blob Storage; hosted deployments using AWS are unaffected. The issue is fixed in version 1.0.4.
Potential Impact
Authenticated app members with workflow execution permissions but without file write/delete permissions can gain unauthorized write and delete access to app content stored in Azure Blob Storage. This could lead to unauthorized modification or deletion of app data. The vulnerability does not affect hosted Flow-Like deployments using AWS storage. The CVSS 4.0 base score is 7.2 (high severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and high impact on integrity and availability.
Mitigation Recommendations
A patch is available in version 1.0.4 that fixes the incorrect authorization issue. Users of self-hosted Rheosoph flow-like deployments using Azure Blob Storage should upgrade to version 1.0.4 or later. Flow-Like Studio and hosted web app users are not affected and require no action. Since this is a self-hosted deployment issue, the vendor does not manage remediation for cloud services. Patch status is confirmed by the vendor advisory.
CVE-2026-50173: CWE-863: Incorrect Authorization in Rheosoph flow-like
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.
CVSS v4.0
Score 7.2high
Affected software
pkg:github/rheosoph/flow-likeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Rheosoph flow-like versions before 1.0.4, the API endpoint GET /api/v1/apps/{app_id}/invoke/presign grants Azure Blob Storage SAS credentials with write and delete permissions to any app member possessing the ExecuteEvents permission, even if they lack ReadFiles and WriteFiles permissions. The endpoint incorrectly treats file permissions as optional after verifying ExecuteEvents, resulting in the Azure credential provider issuing a content SAS token with sp=rwdl (read, write, delete, list) privileges. This allows low-privilege authenticated users to write or delete blobs under the app content prefix. The vulnerability is limited to self-hosted deployments using Azure Blob Storage; hosted deployments using AWS are unaffected. The issue is fixed in version 1.0.4.
Potential Impact
Authenticated app members with workflow execution permissions but without file write/delete permissions can gain unauthorized write and delete access to app content stored in Azure Blob Storage. This could lead to unauthorized modification or deletion of app data. The vulnerability does not affect hosted Flow-Like deployments using AWS storage. The CVSS 4.0 base score is 7.2 (high severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and high impact on integrity and availability.
Mitigation Recommendations
A patch is available in version 1.0.4 that fixes the incorrect authorization issue. Users of self-hosted Rheosoph flow-like deployments using Azure Blob Storage should upgrade to version 1.0.4 or later. Flow-Like Studio and hosted web app users are not affected and require no action. Since this is a self-hosted deployment issue, the vendor does not manage remediation for cloud services. Patch status is confirmed by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-03T20:54:20.433Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a85e65eacd9273b4960cff0
Added to database: 08/19/2026, 17:22:38 UTC
Last enriched: 08/19/2026, 17:37:22 UTC
Last updated: 08/19/2026, 17:43:11 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.