Comparison Overview
Earthbound

Earthbound
156 5th Ave, 10th Floor, New York, NY, US, 10010
Last Update: 14/10/2026
Earthbound Brands is a global licensing, product design, and creative agency. For over 25 years, we’ve partnered with leading retailers and world-renowned brands to expand their reach through strategic brand extensions, innovative product design and development, and t...

WSP
1600, boul. René-Lévesque ouest, 11e étage, Montreal, Quebec, CA, H3H 1P9
Last Update: 05/09/2026
We are one of the world’s leading professional services firms, uniting our engineering, advisory and science-based expertise to shape communities to advance humanity. From local beginnings to a globe-spanning presence today, we operate in over 50 countries and emplo...
Compliance Ranges Comparison

Earthbound







WSP






Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
Earthbound has 42.86% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for WSP in 2026.
Incident History - Earthbound (X = Date, Y = Severity)
Earthbound cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WSP (X = Date, Y = Severity)
WSP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Earthbound

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