Comparison Overview
Brother USA
Brother USA
200 Crossing Blvd, Bridgewater, New Jersey, 08807, US
Last Update: 19/02/2026
Brother is a leading provider of home and office equipment, sewing and crafting products, and industrial solutions. With a legacy spanning over 115 years, our brand is renowned for producing award-winning printers, sewing machines, P-touch labelers, and more. Brother ...
LG Electronics
20 Yeouido-dong, Yeongdeungpo-gu, Seoul, 150-721, KR
Last Update: 05/04/2026
Step into the innovative world of LG Electronics. As a global leader in technology, LG Electronics is dedicated to creating innovative solutions for a better life. Our brand promise, 'Life's Good', embodies our commitment to ensuring a happier, better life for all. W...
Compliance Ranges Comparison
Brother USA
LG Electronics
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Brother USA in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for LG Electronics in 2026.
Incident History - Brother USA (X = Date, Y = Severity)
Brother USA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LG Electronics (X = Date, Y = Severity)
LG Electronics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Brother USA
LG Electronics
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: *.*.