Comparison Overview
B&G

B&G
Navico Ltd. (UK), Templars House, Chandlers Ford, SO53 3TJ, GB
Last Update: 11/03/2026
B&G creates marine electronics for sailors, designed and tested by sailors. Since 1955 B&G has been providing easy to use electronics for the best sailors in the world, from an Ocean Race winner to the day sailor, our electronics help sailors make the most of their time...

Mia propia de mi
N/A
Last Update: 01/04/2026
Empresa privada, dedicada a proveer bienes y servicios de calidad a un amplio sector de la población. Empresa privada, dedicada a proveer bienes y servicios de calidad a un amplio sector de la población. Empresa privada, dedicada a proveer bienes y servicios de calidad...
Compliance Ranges Comparison

B&G







Mia propia de mi






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Electronics Industry Avg (This Year)
No incidents recorded for B&G in 2026.
Incidents vs Consumer Electronics Industry Avg (This Year)
No incidents recorded for Mia propia de mi in 2026.
Incident History - B&G (X = Date, Y = Severity)
B&G cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mia propia de mi (X = Date, Y = Severity)
Mia propia de mi cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

B&G

Mia propia de mi
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: *.*.