Comparison Overview
Canon Australia

Canon Australia
Building A, The Park Estate, Macquarie Park, NSW, 2113, AU
Last Update: 26/01/2026
As the world’s leading imaging organisation, Canon is renowned for innovating and inspiring communities with their extensive range of products and services. From the cameras you take photos with, to the printers in your offices, as well as the extensive market leading t...

TELUS Digital
510 West Georgia Street, Vancouver, V6B 0M3, CA
Last Update: 01/04/2026
TELUS Digital crafts unique and enduring experiences for customers and employees, and creates future-focused digital transformations that stand the test of time. We are the brand behind the brands. Our global team members are both passionate ambassadors of our clients’ ...
Compliance Ranges Comparison

Canon Australia







TELUS Digital






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Canon Australia in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
TELUS Digital has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Canon Australia (X = Date, Y = Severity)
Canon Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TELUS Digital (X = Date, Y = Severity)
TELUS Digital cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Canon Australia

TELUS Digital
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: *.*.