Comparison Overview
Bigman Geophysical, LLC

Bigman Geophysical, LLC
1895 Beaver Ridge Circle, Norcross, 30071, 30071, US
Last Update: 09/01/2026
Bigman Geophysical, LLC offers full-service geophysical and non-destructive testing solutions to the engineering, construction, utility, environmental, and infrastructure industries. We regularly collaborate with customers on the following applications: Archaeological...

Egis
15 avenue du Centre, Saint-Quentin-en-Yvelines , 78286, FR
Last Update: 12/09/2026
Egis is a leading global architectural, consulting, construction engineering, operations and mobility services firm. We create and operate intelligent infrastructure and buildings that both respond to the climate emergency and contribute to balanced, sustainable and res...
Compliance Ranges Comparison

Bigman Geophysical, LLC







Egis






Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Bigman Geophysical, LLC in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Egis in 2026.
Incident History - Bigman Geophysical, LLC (X = Date, Y = Severity)
Bigman Geophysical, LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Egis (X = Date, Y = Severity)
Egis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bigman Geophysical, LLC

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