Comparison Overview
Ruokakesko Oy

Ruokakesko Oy
N/A
Last Update: 12/02/2026
KESKO on suomalainen pörssiyhtiö, joka tuo kauppojensa kautta laatua kuluttajien jokaiseen päivään Pohjoismaissa, Baltiassa, Venäjällä ja Valko-Venäjällä. Kesko ja sen ketjujen kaupat työllistävät yhteensä noin 45 000 henkilöä kahdeksassa maassa. Vastuullisuus on osa jo...

PetSmart
19601 N. 27th Avenue, Phoenix, 85027, US
Last Update: 29/03/2026
At PetSmart, we’ll do Anything for Pets. ❤️🐾 And the people who love them! Because we’re those people, too. Pets inspire and motivate us to bring our best selves to work each day. Our associates are devoted to ensuring that pets’ lives are happy and healthy. So, natura...
Compliance Ranges Comparison

Ruokakesko Oy







PetSmart






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

Ruokakesko Oy

PetSmart
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.