Comparison Overview
Carlsberg Shared Services

Carlsberg Shared Services
ul. Małe Garbary 9, Poznań, undefined, 61-756, PL
Last Update: 30/04/2026
Carlsberg Shared Services provides services to other companies within the Carlsberg Group. Our focus has always been Accounting, but together with the continuous growth of our business, we are now becoming a business center, providing also Planning and Financial Control...

Molson Coors Beverage Company
250 S Wacker Dr, Chicago, Illinois, US, 60606
Last Update: 06/09/2026
From Coors Light, Miller Lite, Molson Canadian, Carling and Staropramen to Coors Banquet, Blue Moon Belgian White, Leinenkugel’s Summer Shandy, Vizzy, Creemore Springs and more, our 16,000+ employees across the globe make and market many of the most beloved beverage bra...
Compliance Ranges Comparison

Carlsberg Shared Services







Molson Coors Beverage Company






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

Carlsberg Shared Services

Molson Coors Beverage 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.