Comparison Overview
Vodacom

Vodacom
Vodacom Corporate Park, 082 Vodacom Boulevard Vodavalley, Midrand, Gauteng, ZA, 1685
Last Update: 01/04/2026
EXTRAA your summer with Vodacom! V-Up on VodaPay and get extra value, extra cash, and extra rewards every day.

Telekom Malaysia
Jalan Pantai Baharu, Kuala Lumpur, 50672, MY
Last Update: 08/09/2026
TM is the national connectivity and digital infrastructure provider and Malaysia’s leading integrated telco; offering a comprehensive suite of communication services and solutions in fixed (telephony and broadband), mobility, content, WiFi, ICT, Cloud and smart services...
Compliance Ranges Comparison

Vodacom







Telekom Malaysia






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

Vodacom

Telekom Malaysia
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.