CVE-2026-50173

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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 v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Azure invoke presign grants app content write SAS to ExecuteEvents-only users · Advisory · Rheosoph/flow-like · GitHub

https://github.com/Rheosoph/flow-like/security/advisories/GHSA-99w9-5gvv-4v78

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-08 07:46 UTCEG score recompute
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-06 21:22 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-06 07:58 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-05 09:33 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-03 16:56 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-10-03 00:42 UTCEG score recompute
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  23. 2026-10-01 22:47 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-09-30 20:51 UTCEG score recompute
Show 70 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-09-30 08:43 UTCEG score recompute
  3. 2026-09-28 21:43 UTCEG score recompute
  4. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-09-27 19:05 UTCEG score recompute
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-09-27 06:57 UTCEG score recompute
  8. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-09-25 00:51 UTCEG score recompute
  11. 2026-09-23 22:05 UTCEG score recompute
  12. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-09-22 21:49 UTCEG score recompute
  14. 2026-09-21 21:32 UTCEG score recompute
  15. 2026-09-20 21:16 UTCEG score recompute
  16. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-19 20:37 UTCEG score recompute
  18. 2026-09-18 20:20 UTCEG score recompute
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-17 21:31 UTCEG score recompute
  21. 2026-09-16 20:06 UTCEG score recompute
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-15 04:18 UTCEG score recompute
  25. 2026-09-14 04:01 UTCEG score recompute
  26. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-09-12 15:36 UTCEG score recompute
  28. 2026-09-11 15:20 UTCEG score recompute
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-09-10 15:02 UTCEG score recompute
  31. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-09 02:35 UTCEG score recompute
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-09-07 18:13 UTCEG score recompute
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-06 17:55 UTCEG score recompute
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  38. 2026-09-05 17:38 UTCEG score recompute
  39. 2026-09-04 17:17 UTCEG score recompute
  40. 2026-09-04 05:09 UTCEG score recompute
  41. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  42. 2026-09-02 16:06 UTCEG score recompute
  43. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  44. 2026-09-01 15:06 UTCEG score recompute
  45. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  46. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-08-31 02:39 UTCEG score recompute
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-08-30 02:23 UTCEG score recompute
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  51. 2026-08-29 01:50 UTCEG score recompute
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-08-27 20:34 UTCEG score recompute
  54. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  55. 2026-08-26 20:11 UTCEG score recompute
  56. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  57. 2026-08-25 19:54 UTCEG score recompute
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  59. 2026-08-24 19:38 UTCEG score recompute
  60. 2026-08-23 07:14 UTCEG score recompute
  61. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  62. 2026-08-22 06:58 UTCEG score recompute
  63. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  64. 2026-08-21 06:42 UTCEG score recompute
  65. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  66. 2026-08-20 06:27 UTCEG score recompute
  67. 2026-08-19 18:18 UTCEG score recompute
  68. 2026-08-19 17:43 UTCEG score recompute
  69. 2026-08-19 17:20 UTCEG score recomputeFirst assessed: 7.2 HIGH
  70. 2026-08-19 17:16 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50173?
CVE-2026-50173 is a high-severity vulnerability; its CVE record was published on August 19, 2026. Flow-Like is a platform for building end-to-end use cases. Prior to version 1.0.4, GET /api/v1/apps/{appid}/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…
When was the CVE record for CVE-2026-50173 published?
The CVE record for CVE-2026-50173 was published on August 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-50173 actively exploited?
CVE-2026-50173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50173?
CVE-2026-50173 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50173?
The CVE record for CVE-2026-50173 names the fix: "Version 1.0.4 patches the issue."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50173

Explore →

Is Your Infrastructure Affected by CVE-2026-50173?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs