Comparison Overview
Qualcomm

Qualcomm
Qualcomm, San Diego, 92121, US
Last Update: 06/07/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.

AMD
2485 Augustine Drive, Santa Clara, 95054, US
Last Update: 16/08/2026
We care deeply about transforming lives with AMD technology to enrich our industry, our communities, and the world. Our mission is to build great products that accelerate next-generation computing experiences – the building blocks for the data center, artificial intelli...
Compliance Ranges Comparison

Qualcomm







AMD






Benchmark & Cyber Underwriting Signals
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
Qualcomm has 18.03% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Semiconductor Manufacturing Industry Avg (This Year)
AMD has 94.17% 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 - AMD (X = Date, Y = Severity)
AMD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Qualcomm

AMD
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.