Comparison Overview
YoSmart/YoLink
YoSmart/YoLink
25172 Arctic Ocean Dr, Lake Forest, 92630, US
Last Update: 27/03/2026
YoLink, by YoSmart, a US corporation based in Irvine, California, is a line of wireless smart products for residential and commercial use, utilizing wireless technology initially utilized for industrial and other large-scale applications. This technology, LoRa, short f...
HARMAN International
400 Atlantic St, Stamford, 06901, US
Last Update: 02/04/2026
Headquartered in Stamford, Connecticut, HARMAN (harman.com) designs and engineers connected products and solutions for automakers, consumers, and enterprises worldwide, including connected car systems, audio and visual products, enterprise automation solutions; and serv...
Compliance Ranges Comparison
YoSmart/YoLink
HARMAN International
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
YoSmart/YoLink has 52.15% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for HARMAN International in 2026.
Incident History - YoSmart/YoLink (X = Date, Y = Severity)
YoSmart/YoLink cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HARMAN International (X = Date, Y = Severity)
HARMAN International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
YoSmart/YoLink
HARMAN International
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: *.*.