Comparison Overview
Neste

Neste
Keilaranta 21, Espoo, Uusimaa, 02150, FI
Last Update: 11/09/2026
To thrive tomorrow, businesses must show meaningful sustainability and climate action today. Neste has done the hard work – we’re ready to help your business fight climate change and reduce greenhouse gas emissions now.

SABIC
PO Box 5101, Riyadh, SA, 11422
Last Update: 06/09/2026
SABIC is a global leader in chemicals headquartered in Riyadh, Saudi Arabia. From making cars and planes more fuel-efficient, to helping conserve the world’s water supply and enabling colorful smartphone cases, we find solutions to the challenges of today to help our cu...
Compliance Ranges Comparison

Neste







SABIC






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

Neste

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