Comparison Overview
SK Telecom

SK Telecom
SK T-Tower, 11, Jung-Gu, 100-999, KR
Last Update: 31/08/2026
SK Telecom has been leading the growth of the mobile industry since 1984. Now, we are taking customer experience to new heights by extending beyond connectivity. By placing AI at the core of its business, we are rapidly transforming into an AI company. We are focusin...

Lumen Technologies
Monroe, Louisiana , US, 71203
Last Update: 15/09/2026
Lumen connects the world. We digitally connect people, data and applications – quickly, securely and effortlessly. Everything we do at Lumen takes advantage of our network strength. From metro connectivity to long-haul data transport to our edge cloud, security, and man...
Compliance Ranges Comparison

SK Telecom







Lumen Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
SK Telecom has 9.89% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Lumen Technologies in 2026.
Incident History - SK Telecom (X = Date, Y = Severity)
SK Telecom cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lumen Technologies (X = Date, Y = Severity)
Lumen Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SK Telecom

Lumen Technologies
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.