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

Comparison Overview

Fraunhofer ITWMFraunhofer ITWM
VS
CNRSCNRS
Fraunhofer ITWM

Fraunhofer ITWM

Fraunhofer-Platz 1, Kaiserslautern, Rheinland-Pfalz 67663, DE

Last Update: 26/04/2026

View Profile
754/1000Fair

Our goal is to further establish mathematics as a key technology, give innovative impetus and implement it in practice together with industry partners. Not only large companies, but also more and more small and medium-sized enterprises use simulations in the most divers...

NAICS:5417
NAICS Definition:Scientific Research and Development Services
Employees:0
Subsidiaries:17
12-month incidents
0
Known data breaches
0
Attack type number
0
CNRS

CNRS

3 rue Michel-Ange, Paris, 75016, FR

Last Update: 01/04/2026

View Profile
Between 750 and 799
https://www.cnrs.fr/
789/1000Fair

The French National Centre for Scientific Research is among the world's leading research institutions. Its scientists explore the living world, matter, the Universe, and the functioning of human societies in order to meet the major challenges of today and tomorrow. Inte...

NAICS:5417
NAICS Definition:Scientific Research and Development Services
Employees:22,365
Subsidiaries:1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Ranges Comparison

Based On Specific Ai Models Category
Fraunhofer ITWM

Fraunhofer ITWM

-
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
CNRS

CNRS

-
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 Research Services Industry Avg (This Year)

No incidents recorded for Fraunhofer ITWM in 2026.

Incidents

Incidents vs Research Services Industry Avg (This Year)

No incidents recorded for CNRS in 2026.

Incidents

Incident History - Fraunhofer ITWM (X = Date, Y = Severity)

Fraunhofer ITWM cyber incidents detection timeline including parent company and subsidiaries.

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

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

CNRS cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
Fraunhofer ITWM

Fraunhofer ITWM

Incidents
No explicit notable incidents reported.
CNRS

CNRS

Incidents
No explicit notable incidents reported.

FAQ

Between Fraunhofer ITWM company and CNRS company, which one has the best AI Cybersecurity Score ?
Between Fraunhofer ITWM company and CNRS company, which one has experienced more cyber incidents in the past ?
Between Fraunhofer ITWM company and CNRS company, which one has experienced more cyber incidents this year ?
Between Fraunhofer ITWM company and CNRS company, which one has experienced at least one ransomware attack ?
Between Fraunhofer ITWM company and CNRS company, which one has experienced at least one data breach ?
Between Fraunhofer ITWM company and CNRS company, which one has experienced at least one targeted cyberattack ?
Between Fraunhofer ITWM company and CNRS company, which one has experienced at least one vulnerability ?
Between Fraunhofer ITWM company and CNRS company, which one holds the most compliance certifications ?
Between Fraunhofer ITWM company and CNRS company, which one holds the fewest compliance certifications ?
Between Fraunhofer ITWM company and CNRS company, which one has the most subsidiaries ?
Between Fraunhofer ITWM company and CNRS company, which one has the largest number of employees ?
Between Fraunhofer ITWM and CNRS, which company holds both SOC 2 Type 1 certifications ?
Between Fraunhofer ITWM and CNRS, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - Fraunhofer ITWM or CNRS ?
Which company is PCI DSS compliant - Fraunhofer ITWM or CNRS ?
Between Fraunhofer ITWM and CNRS, which company complies with HIPAA regulations for healthcare data ?
Between Fraunhofer ITWM and CNRS, 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