Comparison Overview
Mercury Marine
Mercury Marine
W6250 Pioneer Road, Fond du lac, WI, US, 54935
Last Update: 01/04/2026
Mercury Marine® is a world leading manufacturer of marine propulsion systems. A $2.6 billion division of Brunswick Corporation (NYSE: BC), Mercury designs, manufactures and distributes engines, services and parts for recreational, commercial and government marine appli...
EssilorLuxottica
1-6, Rue Paul Cézanne, Paris, FR
Last Update: 02/04/2026
We are EssilorLuxottica, a global leader in the design, manufacture and distribution of advanced vision care products, eyewear and med-tech solutions. Our Mission is to help people around the world to see more and be more by addressing their evolving vision needs, perso...
Compliance Ranges Comparison
Mercury Marine
EssilorLuxottica
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Mercury Marine in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for EssilorLuxottica in 2026.
Incident History - Mercury Marine (X = Date, Y = Severity)
Mercury Marine cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EssilorLuxottica (X = Date, Y = Severity)
EssilorLuxottica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Mercury Marine
EssilorLuxottica
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: *.*.