Comparison Overview
Maroc Telecom

Maroc Telecom
Avenue annakhil, Rabat, 10100, MA
Last Update: 04/04/2026
A significant force in the economic and social development in 10 African countries As a global operator in Africa, a leader in Morocco and other countries, Maroc Telecom is actively involved in the dynamism of the telecommunications sector in 10 African countries where ...

yes
Ha-Yozma St 6, Kfar Saba, 4442218, IL
Last Update: 05/09/2026
תכירו את השחקנים הראשיים שלנו: העובדות והעובדים. אנחנו לא עובדים עם תסריט קבוע, חושבים מחוץ לקופסא, ומייצרים ז'אנר משלנו. כש-יס קמה, בשנת 1998, הבאנו את בשורת הלווין אל עולם שידורי הטלוויזיה והיינו הראשונים להציע שידורים דיגיטליים ושירותי טלוויזיה אינטראקטיביים - כשבח...
Compliance Ranges Comparison

Maroc Telecom







yes






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Maroc Telecom in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for yes in 2026.
Incident History - Maroc Telecom (X = Date, Y = Severity)
Maroc Telecom cyber incidents detection timeline including parent company and subsidiaries.
Incident History - yes (X = Date, Y = Severity)
yes cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Maroc Telecom

yes
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.