Comparison Overview
Rabbit Hole Distillery

Rabbit Hole Distillery
711 E Jefferson St, Louisville, Kentucky, US
Last Update: 12/03/2026
Distilling is baked in Louisville's culture. Rabbit Hole is at the city's creative heart, the NULU district, the nexus of old and new, where artists and entrepreneurs pursue their vision without budgeting for regret. We could be nowhere else. From grain to bottle, insid...

Pernod Ricard
5 cour Paul Ricard, Paris, 75008, FR
Last Update: 07/10/2026
Pernod Ricard is a convivial, responsible and successful global wine and spirits group and the #1 premium spirits organisation in the world. The Group represents 240 premium brands available in more than 160 countries. We are 18,500 exceptionally talented people worldwi...
Compliance Ranges Comparison

Rabbit Hole Distillery







Pernod Ricard






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

Rabbit Hole Distillery

Pernod Ricard
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.