Comparison Overview
Hexagon's Building Solutions

Hexagon's Building Solutions
N/A
Last Update: 04/12/2025
Welcome to Hexagon’s Building Solutions page - Where Vision Takes Shape! At Hexagon’s Building Industry, we stand at the forefront of the construction industry, driving innovation and delivering excellence for every customer. Our vision is to empower construction pr...

Mastercard
2000 Purchase St, Purchase, NY, US, 10577
Last Update: 05/10/2026
Mastercard powers economies and empowers people in 200+ countries and territories worldwide. Together with our customers, we’re building a sustainable economy where everyone can prosper. We support a wide range of digital payments choices, making transactions secure, si...
Compliance Ranges Comparison

Hexagon's Building Solutions







Mastercard






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Hexagon's Building Solutions in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Mastercard has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Hexagon's Building Solutions (X = Date, Y = Severity)
Hexagon's Building Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mastercard (X = Date, Y = Severity)
Mastercard cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hexagon's Building Solutions

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