Comparison Overview
Qualcomm

Qualcomm
Qualcomm, San Diego, 92121, US
Last Update: 07/10/2026
Inspired by 250 years of American ingenuity, we build technologies that expand what’s possible. From wireless to AI at scale and 6G, our innovations power progress worldwide.

STMicroelectronics
39, Chemin du Champ des Filles, C. P. 21, Geneva, Switzerland, CH, CH 1228 Plan-Les-Ouates
Last Update: 14/09/2026
ST is a global semiconductor leader delivering intelligent and energy-efficient products and solutions that power the electronics at the heart of everyday life. ST’s products are found everywhere today, and together with our customers, we are enabling smarter driving an...
Compliance Ranges Comparison

Qualcomm







STMicroelectronics






Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
Qualcomm has 10.31% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
STMicroelectronics has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - Qualcomm (X = Date, Y = Severity)
Qualcomm cyber incidents detection timeline including parent company and subsidiaries.
Incident History - STMicroelectronics (X = Date, Y = Severity)
STMicroelectronics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Qualcomm

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