Comparison Overview
Custom ID Products

Custom ID Products
4301 Aurora Avenue N, Seattle, 98103, US
Last Update: 28/03/2026
Custom I.D. Products, Inc. manufactures and sells high-quality customized identification products. LuckyPet, Inc. and Medic I.D. brands are divisions of Custom I.D. Products. LuckyPet specializes in selling personalized pet identification tags, collars, leashes and a ...

Kellogg Company
One Kellogg Square, Battle Creek, 49017, US
Last Update: 07/10/2026
At Kellanova, our vision is to be the world’s best performing snacks-led powerhouse, unleashing the full potential of our differentiated brands and our passionate people. Powered by our strategy to Differentiate, Drive & Deliver, we are a leading company in global snac...
Compliance Ranges Comparison

Custom ID Products







Kellogg Company






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Custom ID Products in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Kellogg Company in 2026.
Incident History - Custom ID Products (X = Date, Y = Severity)
Custom ID Products cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kellogg Company (X = Date, Y = Severity)
Kellogg Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Custom ID Products

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