Comparison Overview
SQM
SQM
Los Militares 4290, Piso 6, Las Condes, Santiago, CL
Last Update: 24/09/2026
SQM es una compañía chilena con 57 años de historia y una sólida posición económica y financiera. Con más de 9 mil trabajadores (internos y externos) y oficinas comerciales en todo el mundo, exporta sus productos a más de 110 países, y es una de las empresas chilenas de...
Orica
1 Nicholson St, East Melbourne, 3000, AU
Last Update: 20/09/2026
Our story began in 1874, when we first supplied explosives to the Victorian goldfields in Australia. Since then, we have grown to become one of the world’s leading mining and infrastructure solutions providers. From the production and supply of explosives, blasting s...
Compliance Ranges Comparison
SQM
Orica
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for SQM in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Orica in 2026.
Incident History - SQM (X = Date, Y = Severity)
SQM cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orica (X = Date, Y = Severity)
Orica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SQM
Orica
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.