Comparison Overview
Ferrara

Ferrara
404 W Harrison St, Suite 650, Chicago, Illinois, US, 60607
Last Update: 04/04/2026
We are Ferrara, an undisputed leader in sugar confections. Ferrara is #1 in the category in the US with ambitions of being the global leader by leveraging our focus, capabilities, and brand portfolio to drive category development for our community, customer, and consume...

Vedanta Group
Vedanta Resources, London, GB
Last Update: 08/09/2026
We operate on the belief that our people are our core assets and we consistently endeavour towards developing their potential to be our future leaders and key employees. We currently operate in India, South Africa, Liberia and Namibia, through our various subsidiaries. ...
Compliance Ranges Comparison

Ferrara







Vedanta Group






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Ferrara in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
Vedanta Group has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Ferrara (X = Date, Y = Severity)
Ferrara cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vedanta Group (X = Date, Y = Severity)
Vedanta Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ferrara

Vedanta Group
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.