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

PepsiCo
700 Anderson Hill Road, Purchase, 10577, US
Last Update: 07/10/2026
PepsiCo is a playground for curious people. We invite thinkers, doers, and changemakers to champion innovation, take calculated risks, and challenge the status quo. From executives to team members on the front lines, we’re excited about the future. We take chances. Toge...
Compliance Ranges Comparison

Besler







PepsiCo






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)
PepsiCo has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - Besler (X = Date, Y = Severity)
Besler cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PepsiCo (X = Date, Y = Severity)
PepsiCo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Besler

PepsiCo
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.