CVE-2026-78365

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st 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
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to 5.3.2 or later; first tagged release with the fix is v5.5.3."

Authorization Bypass Through User-Controlled Key in the supplier API in Roskus Prospero Flow CRM 4.0.0 through 5.3.1 allows any authenticated user to read and modify another company's supplier record, and to reassign it to their own company, via a PUT request to /api/supplier/{id} setting company_id in the body.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 24, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github_release.
Web page

CVE-2026-78365 · IDOR and missing authorization in Prospero Flow CRM supplier API allows cross-tenant read and modification | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-78365-idor-supplier-api-cross-tenant-update
GitHub release Patch Available

v5.5.3 - Big security upgrade

Patch available: Roskus/prospero-flow-crm v5.5.3

https://github.com/Roskus/prospero-flow-crm/releases/tag/v5.5.3
GitHub commit Patch Available

commit 4a52477e6ed6 (Roskus/prospero-flow-crm)

Patch available: Roskus/prospero-flow-crm v5.5.3 (contains commit 4a52477e6ed6)

https://github.com/Roskus/prospero-flow-crm/commit/4a52477e6ed66afa436814c80e7bcd68670dd596

Vendor Advisories for CVE-2026-78365(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 183× 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.

Showing the most recent 100 of 322 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 222 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78365?
CVE-2026-78365 is a critical-severity vulnerability; its CVE record was published on August 24, 2026. Authorization Bypass Through User-Controlled Key in the supplier API in Roskus Prospero Flow CRM 4.0.0 through 5.3.1 allows any authenticated user to read and modify another company's supplier record, and to reassign it to their own company, via a PUT request to /api/supplier/{id} setting…
When was CVE-2026-78365 made public?
CVE-2026-78365 was made public on August 24, 2026: that is the date its CVE record's CNA, Secur0, gives for when the vulnerability was made public. The CVE record itself was published on August 24, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-78365 actively exploited?
CVE-2026-78365 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78365?
CVE-2026-78365 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78365?
A fix for CVE-2026-78365 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to 5.3.2 or later; first tagged release with the fix is v5.5.3." The vendor advisories EchelonGraph has for CVE-2026-78365 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78365?

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

Book a Demo →Browse All CVEs