Comparison Overview
International Container Terminal Services, Inc.

International Container Terminal Services, Inc.
Manila, 1012, PH
Last Update: 07/10/2026
International Container Terminal Services, Inc. (ICTSI) is the largest independent terminal operator across six continents. ICTSI builds and operates efficient and sustainable origin and destination gateway terminals in markets where we can leverage our competitive st...

Evri
Evri, Morley, Leeds, LS27 0WH, GB
Last Update: 14/09/2026
Need some help? Get in touch with our friendly team at https://bit.ly/evriwebsite3 Every parcel, every person, every place. Evri Group brings together Evri, DHL eCommerce UK – which in 2026 will be rebranded Evri Premium, a network of DHL - customs clearance and logist...
Compliance Ranges Comparison

International Container Terminal Services, Inc.







Evri






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for International Container Terminal Services, Inc. in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Evri in 2026.
Incident History - International Container Terminal Services, Inc. (X = Date, Y = Severity)
International Container Terminal Services, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Evri (X = Date, Y = Severity)
Evri cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

International Container Terminal Services, Inc.

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