Comparison Overview
L3 Technologies

L3 Technologies
600 Third Ave, New York, 10016, US
Last Update: 30/03/2026
With headquarters in New York City and approximately 31,000 employees worldwide, L3 develops advanced defense technologies and commercial solutions in pilot training, aviation security, night vision and EO/IR, weapons, maritime systems and space. The company reported 20...

Thales
6, Rue de la Verrerie, Meudon, 92190, FR
Last Update: 12/09/2026
Thales (Euronext Paris: HO) is a global leader in advanced technologies for the Defence, Aerospace, and Cyber & Digital sectors. Its portfolio of innovative products and services addresses several major challenges: sovereignty, security, sustainability and inclusion. T...
Compliance Ranges Comparison

L3 Technologies







Thales






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for L3 Technologies in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Thales has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - L3 Technologies (X = Date, Y = Severity)
L3 Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Thales (X = Date, Y = Severity)
Thales cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

L3 Technologies

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