Comparison Overview
Hexagon AB

Hexagon AB
Lilla Bantorget 15, Stockholm, SE-103 59, SE
Last Update: 26/11/2025
At Hexagon, we don’t just measure the world – we define its future. As the global leader in measurement technologies, we provide the confidence that vital industries rely on to build, navigate, and innovate. From microns to Mars, our solutions drive productivity,...

Softtek
Ave. Constitución 3098 Col. Santa María, 6th Floor, Monterrey, Nuevo Leon, MX, 64650
Last Update: 02/04/2026
Founded in 1982 by a small group of entrepreneurs, Softtek started out in Mexico providing local IT services, and today is a global leader in next-generation digital solutions. The first company to introduce the Nearshore model, Softtek helps Global 2000 organizations b...
Compliance Ranges Comparison

Hexagon AB







Softtek






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Hexagon AB in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Softtek in 2026.
Incident History - Hexagon AB (X = Date, Y = Severity)
Hexagon AB cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Softtek (X = Date, Y = Severity)
Softtek cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hexagon AB

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