Comparison Overview
Bourne Steel

Bourne Steel
St Clements House, St Clements Road, Poole, BH12 4GP, GB
Last Update: 02/02/2026
From new build and refurbishment projects to Energy from Waste and Combined Cycle Gas Turbine power plants, we take highly technical and logistically challenging projects in our stride. We have a reputation for quality. It stems from our workshop skills, is enhanced by...

GMR Group
New Udaan Bhawan, New Delhi, 110037, IN
Last Update: 07/10/2026
GMR Group is a leading Indian infrastructure conglomerate with a diversified presence across Airports, Energy, Transportation, Urban Infrastructure, and Sports. With over two decades of experience, the Group has built world-class assets and pioneered innovations in sust...
Compliance Ranges Comparison

Bourne Steel







GMR Group






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

Bourne Steel

GMR Group
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.