Comparison Overview
Ingram Micro

Ingram Micro
3351 Michelson Drive, Suite 100, Irvine, 92612, US
Last Update: 14/09/2026
Ingram Micro is a leading technology company for the global information technology ecosystem. With the ability to reach nearly 90% of the global population, we play a vital role in the worldwide IT sales channel, bringing products and services from technology manufactur...

SoftwareOne
Riedenmatt 4, Stans, CH, 6370
Last Update: 11/09/2026
SoftwareOne is a global software and cloud solutions provider. With a presence in over 70 countries and a team of around 13,000 professionals, we combine global scale and local expertise to help clients optimize costs, accelerate growth, and navigate complex IT environm...
Compliance Ranges Comparison

Ingram Micro







SoftwareOne






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Ingram Micro has 32.43% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for SoftwareOne in 2026.
Incident History - Ingram Micro (X = Date, Y = Severity)
Ingram Micro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SoftwareOne (X = Date, Y = Severity)
SoftwareOne cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ingram Micro

SoftwareOne
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)