Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

Bell Cause pour la causeBell Cause pour la cause
VS
NokiaNokia
Bell Cause pour la cause

Bell Cause pour la cause

1. carrefour Alexander-Graham-Bell, Verdun, H3E 3B3, CA

Last Update: 21/04/2026

View Profile
Between 750 and 799
http://www.bell.ca/cause
755/1000Fair

"Bell Cause pour la cause, l’engagement le plus important jamais pris par une entreprise envers la santé mentale au Canada, mise sur quatre piliers clés : la lutte contre la stigmatisation, l’accès aux soins, la recherche et le leadership en milieu de travail. Cet engag...

NAICS:517
NAICS Definition:Telecommunications
Employees:None
Subsidiaries:6
12-month incidents
0
Known data breaches
0
Attack type number
0
Nokia

Nokia

Karakaari 7, Espoo, Southern Finland, FI, 02610

Last Update: 01/04/2026

View Profile
Between 800 and 849
https://www.nokia.com
802/1000Good

Nokia is a global leader in connectivity for the AI era. With expertise across fixed, mobile, and transport networks, powered by the innovation of Nokia Bell Labs, we’re advancing connectivity to secure a brighter world. Advanced connectivity is key to enable the oppor...

NAICS:517
NAICS Definition:Telecommunications
Employees:100,250
Subsidiaries:6
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Ranges Comparison

Based On Specific Ai Models Category
Bell Cause pour la cause

Bell Cause pour la cause

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
Nokia

Nokia

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Avg (This Year)

No incidents recorded for Bell Cause pour la cause in 2026.

Incidents

Incidents vs Telecommunications Industry Avg (This Year)

No incidents recorded for Nokia in 2026.

Incidents

Incident History - Bell Cause pour la cause (X = Date, Y = Severity)

Bell Cause pour la cause cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - Nokia (X = Date, Y = Severity)

Nokia cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
Bell Cause pour la cause

Bell Cause pour la cause

Incidents
No explicit notable incidents reported.
Nokia

Nokia

Incidents
🔒 Incident : Cyber Attack
NOK000031025

FAQ

Between Bell Cause pour la cause company and Nokia company, which one has the best AI Cybersecurity Score ?
Between Bell Cause pour la cause company and Nokia company, which one has experienced more cyber incidents in the past ?
Between Bell Cause pour la cause company and Nokia company, which one has experienced more cyber incidents this year ?
Between Bell Cause pour la cause company and Nokia company, which one has experienced at least one ransomware attack ?
Between Bell Cause pour la cause company and Nokia company, which one has experienced at least one data breach ?
Between Bell Cause pour la cause company and Nokia company, which one has experienced at least one targeted cyberattack ?
Between Bell Cause pour la cause company and Nokia company, which one has experienced at least one vulnerability ?
Between Bell Cause pour la cause company and Nokia company, which one holds the most compliance certifications ?
Between Bell Cause pour la cause company and Nokia company, which one holds the fewest compliance certifications ?
Between Bell Cause pour la cause company and Nokia company, which one has the most subsidiaries ?
Between Bell Cause pour la cause company and Nokia company, which one has the largest number of employees ?
Between Bell Cause pour la cause and Nokia, which company holds both SOC 2 Type 1 certifications ?
Between Bell Cause pour la cause and Nokia, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - Bell Cause pour la cause or Nokia ?
Which company is PCI DSS compliant - Bell Cause pour la cause or Nokia ?
Between Bell Cause pour la cause and Nokia, which company complies with HIPAA regulations for healthcare data ?
Between Bell Cause pour la cause and Nokia, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-49416
SUMMARY

The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49414
SUMMARY

The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49417
SUMMARY

Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49413
SUMMARY

The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49412
SUMMARY

The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory. An unprivileged local user can exploit this use-after-free to escalate privileges.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA