Comparison Overview
Asahi Group Holdings

Asahi Group Holdings
1-23-1, Azumabashi, Sumida-ku, Tokyo, JP, 1308602
Last Update: 08/10/2026
Asahi Group Holdings, Ltd. is a global leader offering a diverse collection of brands centered on beer, alcohol and non-alcohol beverages, and food. Our vision is to be the leader in creating shared moments full of life with great taste. Established in Japan in 1889, th...

UNFI
313 Iron Horse Way, Providence, RI, US, 02908
Last Update: 02/04/2026
UNFI is North America’s Premier Food Wholesaler. We transform the world of food for our associates, customers, suppliers and the families we serve every day. With deeper full store selection and compelling brands for every aisle, built on an unmatched heritage in gre...
Compliance Ranges Comparison

Asahi Group Holdings







UNFI






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
Asahi Group Holdings has 3.09% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for UNFI in 2026.
Incident History - Asahi Group Holdings (X = Date, Y = Severity)
Asahi Group Holdings cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UNFI (X = Date, Y = Severity)
UNFI cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Asahi Group Holdings

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