Comparison Overview
Huawei Consumer Business Group
Huawei Consumer Business Group
Huawei Technologies Co., Ltd., Bantian, Longgang District, Shenzhen, Guangdong, CN
Last Update: 27/01/2026
Huawei Technologies Co. offers products and services in more than 170 countries, serving a third of the world’s population. As one of Huawei’s three primary business units, Huawei Consumer Business Group became the world’s third-biggest smartphone maker in 2015, deliver...
Canon USA
One Canon Park, Melville, NY, US, 11747
Last Update: 03/04/2026
Living and Working Together For The Common Good... - Kyosei Kyosei unites Canon and its employees in contributing to the prosperity of humanity and the protection of the world we share. As a leading provider of consumer, business-to-business, and industrial digital ...
Compliance Ranges Comparison
Huawei Consumer Business Group
Canon USA
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Huawei Consumer Business Group in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Canon USA in 2026.
Incident History - Huawei Consumer Business Group (X = Date, Y = Severity)
Huawei Consumer Business Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Canon USA (X = Date, Y = Severity)
Canon USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Huawei Consumer Business Group
Canon USA
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: *.*.