Comparison Overview

Beacon Data, Inc.
23 Old Kings Hwy S, Darien, 06820, US
Last Update: 07/08/2026
Beacon is a expert data services company who serves as a guiding light to companies serious about digital transformation and turning their data into strategic advantage. Tech and business leaders call our data practitioners to help architect and implement their modern ...

Thoughtworks
200 E Randolph St, 25th Floor, Chicago, IL, US, 60601-6501
Last Update: 14/09/2026
We are a global technology consultancy that delivers extraordinary impact by blending design, engineering and AI expertise. For 30 years, our commitment to design-led thinking, engineering excellence and innovation means we prioritize people, build teams with strong te...
Compliance Ranges Comparison
Beacon Data, Inc.







Thoughtworks






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

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