Comparison Overview
LSEG Technology

LSEG Technology
No, 1, Millennium Drive, Malambe, 10115, LK
Last Update: 02/04/2026
Part of London Stock Exchange Group (LSEG), LSEG Technology develops and operates high performance technology solutions, including trading, market surveillance and post trade systems for over 40 organisations and exchanges, including the Group’s own markets. LSEG (Lond...

Inetum
5, Rue Touzet Gaillard, St.-Ouen, Île-de-France, FR, 93400
Last Update: 07/09/2026
Inetum is a European leader in digital services. Inetum’s team of 27,000 consultants and specialists strive every day to make a digital impact for businesses, public sector entities and society. Inetum’s solutions aim at contributing to its clients’ performance and inno...
Compliance Ranges Comparison

LSEG Technology







Inetum






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for LSEG Technology in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Inetum in 2026.
Incident History - LSEG Technology (X = Date, Y = Severity)
LSEG Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Inetum (X = Date, Y = Severity)
Inetum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

LSEG Technology

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