CVE-2026-78365 Roskus CVE debrief

Who should care

Organizations using Roskus Prospero Flow CRM 4.0.0 through 5.3.1, particularly those with multiple companies or suppliers configured in the system, should be aware of this vulnerability and take steps to mitigate it. Affected operators, platforms, and security teams should prioritize patching to prevent potential unauthorized access to supplier records.

Technical summary

The CVE-2026-78365 vulnerability is an authorization bypass issue in the supplier API of Roskus Prospero Flow CRM versions 4.0.0 through 5.3.1. An authenticated user can exploit this vulnerability by sending a PUT request to /api/supplier/{id} with a modified company_id in the body, allowing them to read and modify supplier records belonging to other companies, and reassign them to their own company. This issue has a CVSS score of 9.3 and a severity of CRITICAL.

Defensive priority

Organizations using Roskus Prospero Flow CRM 4.0.0 through 5.3.1 should prioritize patching to prevent potential unauthorized access to supplier records.

Recommended defensive actions

• Apply patches or updates provided by the vendor to address the authorization bypass vulnerability
• Restrict access to the supplier API to only authorized users
• Monitor API requests for suspicious activity
• Implement additional security controls, such as input validation and access controls
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE-2026-78365 vulnerability is an authorization bypass issue in the supplier API of Roskus Prospero Flow CRM versions 4.0.0 through 5.3.1. Evidence is limited, and further verification is needed to determine the full scope of affected systems and potential impact. Defenders should verify the presence of affected product deployments in managed environments, review official advisories or CVE records, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.