Comparison Overview
McKim & Creed, Inc.

McKim & Creed, Inc.
1730 Varsity Drive, Suite 500, Raleigh, NC, US, 27606
Last Update: 30/03/2026
What if you had the opportunity to do something you love and make a difference in peoples' lives at the same time? As engineers and surveyors, we use some pretty cool tools (think LiDAR, unmanned aerial systems [UAS], modeling, etc.) to solve some of today’s (and tomo...

Ventia
155 Miller St, Level 27, North Sydney, New South Wales, AU, 2060
Last Update: 13/09/2026
Ventia provides essential services to make infrastructure work for communities in Australia and New Zealand. We pride ourselves on safe and sustainable services for our corporate and government clients across a broad range of sectors, including transport, telecommunic...
Compliance Ranges Comparison

McKim & Creed, Inc.







Ventia






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

McKim & Creed, Inc.

Ventia
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.