Comparison Overview

Qualcomm

VS

EE

Qualcomm

Qualcomm, San Diego, CA, 92121, US
Last Update: 2025-12-09
Between 800 and 849

Delivering intelligent computing everywhere.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 45,945
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
1

EE

undefined, London , undefined, undefined, GB
Last Update: 2025-12-09
Between 750 and 799

EE, part of BT Group, is the largest and most advanced mobile communications company in the UK, delivering mobile and fixed communications services to consumers. We run the UK's biggest and fastest mobile network, having pioneered the UK's first superfast 4G mobile service in October 2012 and was the first European operator to surpass 14 million 4G customers in December 2015. We have more than 550 shops across the UK and we’re dedicated to making EE an outstanding place to work for our 13,000 employees. Our 4G coverage reaches 80% of the UK geography and we have plans to extend 4G geographic coverage to 95% by 2020. We’ve received extensive independent recognition, including being ranked the UK's best overall network by RootMetrics®; Best Network at the 2015, 2016 and 2017 Mobile News Awards; Best Network at the Mobile Choice Consumer Awards 2016; Best Consumer Network at the 2015 & 2016 Mobile Industry Awards; as well as Fastest Network and Best Network Coverage at the 2017 uSwitch Mobile Awards.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 11,299
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/qualcomm.jpeg
Qualcomm
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/ee-uk.jpeg
EE
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Qualcomm
100%
Compliance Rate
0/4 Standards Verified
EE
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Qualcomm in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for EE in 2025.

Incident History — Qualcomm (X = Date, Y = Severity)

Qualcomm cyber incidents detection timeline including parent company and subsidiaries

Incident History — EE (X = Date, Y = Severity)

EE cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/qualcomm.jpeg
Qualcomm
Incidents

Date Detected: 8/2024
Type:Vulnerability
Attack Vector: GPU Driver Exploitation
Motivation: Full Device Control
Blog: Blog
https://images.rankiteo.com/companyimages/ee-uk.jpeg
EE
Incidents

Date Detected: 12/2024
Type:Ransomware
Blog: Blog

Date Detected: 05/2018
Type:Data Leak
Attack Vector: Exposed Default Password
Motivation: Unintentional Exposure
Blog: Blog

FAQ

Qualcomm company demonstrates a stronger AI Cybersecurity Score compared to EE company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

EE company has faced a higher number of disclosed cyber incidents historically compared to Qualcomm company.

In the current year, EE company and Qualcomm company have not reported any cyber incidents.

EE company has confirmed experiencing a ransomware attack, while Qualcomm company has not reported such incidents publicly.

Neither EE company nor Qualcomm company has reported experiencing a data breach publicly.

Neither EE company nor Qualcomm company has reported experiencing targeted cyberattacks publicly.

Qualcomm company has disclosed at least one vulnerability, while EE company has not reported such incidents publicly.

Neither Qualcomm nor EE holds any compliance certifications.

Neither company holds any compliance certifications.

EE company has more subsidiaries worldwide compared to Qualcomm company.

Qualcomm company employs more people globally than EE company, reflecting its scale as a Telecommunications.

Neither Qualcomm nor EE holds SOC 2 Type 1 certification.

Neither Qualcomm nor EE holds SOC 2 Type 2 certification.

Neither Qualcomm nor EE holds ISO 27001 certification.

Neither Qualcomm nor EE holds PCI DSS certification.

Neither Qualcomm nor EE holds HIPAA certification.

Neither Qualcomm nor EE holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N