Comparison Overview
Worldwide Logistics Group UK

Worldwide Logistics Group UK
Unit 16 Thames Gateway Park, Dagenham, RM9 6FB, GB
Last Update: 22/11/2025
At Worldwide Logistics Group our mission is to re-write how the forwarding industry works and for our peers to aspire to our level of transparency. We want to make you part of our Worldwide Logistics family, acting as your partner and understanding your business needs. ...

John Swire & Sons (H.K.) Ltd.
Hong Kong, HK
Last Update: 14/09/2026
Swire is a highly diversified global business group which has been in operation for over 200 years. It employs over 121,000 people across the world. Swire Group’s businesses span Property, Beverages & Food Chain, Aviation, Marine Services, Trading & Industrial, as well ...
Compliance Ranges Comparison

Worldwide Logistics Group UK







John Swire & Sons (H.K.) Ltd.






Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for Worldwide Logistics Group UK in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for John Swire & Sons (H.K.) Ltd. in 2026.
Incident History - Worldwide Logistics Group UK (X = Date, Y = Severity)
Worldwide Logistics Group UK cyber incidents detection timeline including parent company and subsidiaries.
Incident History - John Swire & Sons (H.K.) Ltd. (X = Date, Y = Severity)
John Swire & Sons (H.K.) Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Worldwide Logistics Group UK

John Swire & Sons (H.K.) Ltd.
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.