Comparison Overview
The Building Intelligence Group

The Building Intelligence Group
PO Box 830, Wellington, 6140, NZ
Last Update: 05/01/2026
The Building Intelligence Group is 35 years strong in independent project management and advisory services. We’re a New Zealand company, 100% owned by people who work in the business and proud of it. Operating from 13 locations across the motu means we can service proje...

Bouygues Construction
Challenger, Saint-Quentin-en-Yvelines, 78 280, FR
Last Update: 15/09/2026
Bouygues Construction employs 35,600 people around the world, all driven by the greatest and most exciting responsibility of all – building for life. For our customers in more than 50 countries, we deliver much more than projects. We build to create spaces, connectio...
Compliance Ranges Comparison

The Building Intelligence Group







Bouygues Construction






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for The Building Intelligence Group in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Bouygues Construction in 2026.
Incident History - The Building Intelligence Group (X = Date, Y = Severity)
The Building Intelligence Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bouygues Construction (X = Date, Y = Severity)
Bouygues Construction cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

The Building Intelligence Group

Bouygues Construction
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.