Comparison Overview
Mastercom Australia

Mastercom Australia
136 Railway Parade, Granville, New South Wales, AU, 2142
Last Update: 14/04/2026
For over 50 years, Mastercom has worked with teams in all situations, from the factory floor to the fireground. Communication is in Mastercom's DNA, bringing together devices, new technology, networks and software that enable teams to work seamlessly. Mastercom engineer...

Vodafone
1 Kingdom Street, London, W2 6BY, GB
Last Update: 08/09/2026
At Vodafone, our purpose is to connect everyone. From the seabed to the stars, we provide innovative mobile and fixed connectivity solutions to empower our customers across the globe. And we're constantly expanding coverage to bridge continents and spread inclusion, eve...
Compliance Ranges Comparison

Mastercom Australia







Vodafone






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Mastercom Australia has 47.09% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
Vodafone has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - Mastercom Australia (X = Date, Y = Severity)
Mastercom Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vodafone (X = Date, Y = Severity)
Vodafone cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Mastercom Australia

Vodafone
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout