Comparison Overview
Bosch Vietnam

Bosch Vietnam
33 Le Duan Street, Ben Nghe Ward, District 1, Ho Chi Minh City, 70000, VN
Last Update: 01/04/2026
Bosch first started in Vietnam with a representative office in 1994 and since 2007 the company is represented by Robert Bosch (Vietnam) Co. Ltd. Bosch has its main office in Ho Chi Minh City, with branch offices in Hanoi and Da Nang, and a Powertrain Solutions plant in ...

thyssenkrupp
thyssenkrupp Allee 1, Essen, 45143, DE
Last Update: 23/09/2026
thyssenkrupp is an international industrial and technology group with more than 93,000 employees. In the fiscal year 2024/2025, the company generated sales of around €33 billion in 48 countries. Its business activities are bundled in five segments: Automotive Technology...
Compliance Ranges Comparison

Bosch Vietnam







thyssenkrupp






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Bosch Vietnam in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for thyssenkrupp in 2026.
Incident History - Bosch Vietnam (X = Date, Y = Severity)
Bosch Vietnam cyber incidents detection timeline including parent company and subsidiaries.
Incident History - thyssenkrupp (X = Date, Y = Severity)
thyssenkrupp cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bosch Vietnam

thyssenkrupp
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.