Comparison Overview
Yara Hellas

Yara Hellas
137 Leoforos Syngrou, Nea Smyrni, Attiki, 171 21, GR
Last Update: 03/12/2025
Σχετικά με τη Yara Αποστολή της Yara είναι να θρέψει υπεύθυνα τον παγκόσμιο πληθυσμό και παράλληλα να συμβάλλει στην προστασία του πλανήτη. Ακολουθούμε μια στρατηγική βιώσιμης ανάπτυξης, μέσω της μείωσης των εκπομπών από την παραγωγή προϊόντων θρέψης και την ανάπτυξη λ...

UPL
UPL House, Mumbai, 400051, IN
Last Update: 08/09/2026
UPL Ltd. (NSE: UPL & BSE: 512070) is a global provider of sustainable agriculture products & solutions, with annual revenue exceeding $5 billion. As one of the top 5 agriculture solutions companies worldwide, our robust portfolio consists of biologicals and traditional ...
Compliance Ranges Comparison

Yara Hellas







UPL






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

Yara Hellas

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