Comparison Overview
Yandex

Yandex
16, Leo Tolstoy St, Moscow, 119021, RU
Last Update: 29/03/2026
Yandex is a technology company that builds intelligent products and services powered by machine learning. Our goal is to help consumers and businesses better navigate the online and offline world. Since 1997, we have delivered world-class, locally relevant search and in...

foodpanda
63 Robinson Road, Singapore, 068894, SG
Last Update: 15/09/2026
At foodpanda, we're on a mission to redefine how food, people, culture and tech are connected. Our panda family consists of problem solvers, designers and thinkers, working around the clock to make foodpanda the most powerful online tool for food convenience in the univ...
Compliance Ranges Comparison

Yandex







foodpanda






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

Yandex

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