CVE-2026-59233

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th 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

Also known asEUVD-2026-55618 (ENISA EUVD) · GHSA-4fxp-2m36-qv64 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to version 5.2.1 or higher."

Missing Authorization in the permission management component in Roskus Prospero Flow CRM before 5.2.1 allows any authenticated user to grant any role, including their own, the complete set of application permissions via a crafted POST request to the permission save endpoint, which performs no authorization check before synchronizing the submitted permissions to the specified role.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 10, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Aug 10, 2026
Patch available. Sources: github_commit, github_release.
Web page

CVE-2026-59233 · Missing Authorization in Prospero Flow CRM allows any authenticated user to escalate privileges via the permission save endpoint | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-59233-missing-authorization-in-prospero-flow-crm-permission-endpoint
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 86a7d6557bd1 (Roskus/prospero-flow-crm)

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

https://github.com/Roskus/prospero-flow-crm/commit/86a7d6557bd111518a221f4575ad6e36087e19d3

Vendor Advisories for CVE-2026-59233(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 36× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 256 rows 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 156 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-59233?
CVE-2026-59233 is a high-severity vulnerability; its CVE record was published on August 10, 2026. Missing Authorization in the permission management component in Roskus Prospero Flow CRM before 5.2.1 allows any authenticated user to grant any role, including their own, the complete set of application permissions via a crafted POST request to the permission save endpoint, which performs no…
When was CVE-2026-59233 made public?
CVE-2026-59233 was made public on August 10, 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 10, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-59233 actively exploited?
CVE-2026-59233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59233?
CVE-2026-59233 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59233?
A fix for CVE-2026-59233 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 version 5.2.1 or higher." The vendor advisories EchelonGraph has for CVE-2026-59233 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59233?

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