Comparison Overview
BlueParrott
BlueParrott
900 Chelmsford St., Lowell, MA, 01851, US
Last Update: 30/11/2025
On-the-road every word gets heard, anywhere you go. Like never before, business is on the move. Mobile professionals have to stay in touch, and in reach, no matter where they go. Our BlueParrott headsets, long the favorite of professional truck drivers, are strong and ...
Telekom Malaysia
Jalan Pantai Baharu, Kuala Lumpur, 50672, MY
Last Update: 01/04/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
BlueParrott
Telekom Malaysia
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for BlueParrott in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telekom Malaysia in 2026.
Incident History - BlueParrott (X = Date, Y = Severity)
BlueParrott 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
BlueParrott
Telekom Malaysia
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.