Comparison Overview
Besler
Besler
Ferah Caddesi, Üsküdar, Istanbul, TR, 34692
Last Update: 25/02/2026
Yıldız Holding'in halka açık ikinci büyük gıda şirketi olan Besler, 16 farklı kategoride yaklaşık 1.500 ürün ve 57 markası ile her yıl yaklaşık 61 milyon tabakta 19,5 milyon haneye misafir oluyor. Kurulduğumuz ilk günden bu yana, şirketimiz ve bağlı ortaklıklarımızla b...
Nestlé
Av. Nestlé 55, Vevey, CH, 1800
Last Update: 07/10/2026
As the world’s largest food and beverage company we are driven by a simple aim: unlocking the power of food to enhance quality of life for everyone, today and for generations to come. To deliver on this, we serve with passion, with a spirit of excellence, offering produ...
Compliance Ranges Comparison
Besler
Nestlé
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Besler in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Nestlé in 2026.
Incident History - Besler (X = Date, Y = Severity)
Besler cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nestlé (X = Date, Y = Severity)
Nestlé cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Besler
Nestlé
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.