Comparison Overview
Modaxo

Modaxo
5060 Spectrum Way, Mississauga, Ontario, L4W 5N5, CA
Last Update: 29/04/2026
Modaxo brings together businesses focused on providing the technologies that move the world’s people each and every day. Working both together and independently, our businesses are focused on one thing – delivering software and technology solutions that help connect ...

Sage
North Park, Newcastle upon Tyne, GB, NE13 9AA
Last Update: 03/09/2026
At Sage, we knock down barriers with information, insights, and tools to help your business flow. We provide businesses with software and services that are simple and easy to use, as we work with you to give you that feeling of confidence. Customers trust our Payroll,...
Compliance Ranges Comparison

Modaxo







Sage






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Modaxo in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Sage in 2026.
Incident History - Modaxo (X = Date, Y = Severity)
Modaxo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sage (X = Date, Y = Severity)
Sage cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Modaxo

Sage
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.