Comparison Overview
Nutiani

Nutiani
109 Fanshawe St, Auckland, 1010, NZ
Last Update: 25/05/2026
We offer end-to-end solutions through a combination of high performing, science-backed specialty ingredients, tested- concepts and expert services grounded in the science of the human body, to help consumers and patients to live a longer, more fulfilling, healthier life...

Arla Foods
Sønderhøj 14, Viby, DK, 8260
Last Update: 13/09/2026
We are more than 23,000 colleagues across 39 countries and 7,624 dairy farmer-owners in Denmark, Sweden, United Kingdom, Germany, Belgium, Luxembourg, and the Netherlands. We aim to create the future of dairy, to bring healthy and sustainable dairy products to people ac...
Compliance Ranges Comparison

Nutiani







Arla Foods






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

Nutiani

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