Comparison Overview
AB InBev Korea 오비맥주

AB InBev Korea 오비맥주
8F, 517, Yeongdong-daero , Gangnam-gu, Seoul, 06164, KR
Last Update: 28/10/2025
We are a company of owners. We believe that you get out what you put in. We strive to be the best. Pursuing our Dream, committed to improving lives for more people in more communities. For centuries, we’ve been bringing people together, through sports, through music an...

Levy Restaurants
980 N Michigan Ave, Chicago, 60611, US
Last Update: 16/09/2026
Discover the Levy Difference Passion is a great gift, and we have a lot of gifted people. Our contagious enthusiasm stimulates minds, engages senses and touches hearts. Each guest is greeted with a warm welcome, served with pride and extended a heartfelt invitation t...
Compliance Ranges Comparison

AB InBev Korea 오비맥주







Levy Restaurants






Benchmark & Cyber Underwriting Signals
Incidents vs Food & Beverages Industry Avg (This Year)
No incidents recorded for AB InBev Korea 오비맥주 in 2026.
Incidents vs Food & Beverages Industry Avg (This Year)
No incidents recorded for Levy Restaurants in 2026.
Incident History - AB InBev Korea 오비맥주 (X = Date, Y = Severity)
AB InBev Korea 오비맥주 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Levy Restaurants (X = Date, Y = Severity)
Levy Restaurants cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AB InBev Korea 오비맥주

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