Comparison Overview
CenturyLink Business

CenturyLink Business
100 Centurylink Drive, None, Monroe, Louisiana, US, 71203
Last Update: 09/03/2026
We are an innovative telecommunications company with a nationwide footprint and a passion for empowering the small businesses that power the communities we serve. And because businesses come in many shapes and sizes, our solutions do, too. Visit our website to learn mo...

ZTE Corporation
ZTE Corporation Hi-Tech Road South, Shenzhen, 518057, CN
Last Update: 07/09/2026
ZTE connects the world with continuous innovation for a better future. The company provides innovative technologies and integrated solutions, and its portfolio spans communication networks, computing infrastructure, industry digital solutions, and personal and home sm...
Compliance Ranges Comparison

CenturyLink Business







ZTE Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for CenturyLink Business in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for ZTE Corporation in 2026.
Incident History - CenturyLink Business (X = Date, Y = Severity)
CenturyLink Business cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ZTE Corporation (X = Date, Y = Severity)
ZTE Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CenturyLink Business

ZTE Corporation
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.