Comparison Overview
AECOM - Government

AECOM - Government
13355 Noel Rd, Dallas, Texas, 75240, US
Last Update: 11/02/2026
We have proudly partnered with government and defense organizations for more than 100 years to deliver innovative solutions for mission success. Working to safeguard our nations and communities for a better, more resilient world, our experts provide comprehensive infras...

Technip Energies
Paris, FR
Last Update: 14/09/2026
Technip Energies is a global technology and engineering powerhouse. With leadership positions in LNG, hydrogen, ethylene, sustainable chemistry, and CO2 management, we are contributing to the development of critical markets such as energy, energy derivatives, decarbon...
Compliance Ranges Comparison

AECOM - Government







Technip Energies






Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for AECOM - Government in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for Technip Energies in 2026.
Incident History - AECOM - Government (X = Date, Y = Severity)
AECOM - Government cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Technip Energies (X = Date, Y = Severity)
Technip Energies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AECOM - Government

Technip Energies
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.