Comparison Overview
Audi St-Bruno

Audi St-Bruno
1917 Boulevard Sir-Wilfrid-Laurier, St-Bruno, Quebec J3V 0G8, CA
Last Update: 11/04/2026
Audi St-Bruno has been proudly serving the Saint-Bruno-de-Montarville, Québec community since 1977 as a premier Audi Dealership specialising in New & Used Audi Vehicle Sales, Service and Parts. Dedicated to helping you find the perfect vehicle for you; whether it is ne...

Royal Enfield
Eicher Motors, #96, Sector 32,, Gurgaon, 122001, IN
Last Update: 13/09/2026
The oldest motorcycle brand in continuous production, Royal Enfield made its first motorcycle in 1901. A division of Eicher Motors Limited, Royal Enfield has created the mid-sized motorcycle segment in India with its unique and distinctive modern classic bikes. Royal ...
Compliance Ranges Comparison

Audi St-Bruno







Royal Enfield






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

Audi St-Bruno

Royal Enfield
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.