Comparison Overview
Metalsa
Metalsa
Calle Benito Juárez 1102 Pte, Centro, Monterrey, N.L., Piso 46, Monterrey, Nuevo León, MX, 64000
Last Update: 05/02/2026
Metalsa is a private company and a subsidiary of Proeza Group. We manufacture tier-1 structural components for the light and commercial vehicle markets. We are constantly growing and innovating, and our state-of-the-art technology keeps our products at the forefront. ...
Mercedes-Benz USA
303 Perimeter Center North, Atlanta, 30346, US
Last Update: 17/06/2026
Mercedes-Benz USA, LLC (MBUSA), a Daimler Company, is responsible for the Distribution and Marketing of Mercedes-Benz and smart products in the United States. MBUSA was founded in 1965 and prior to that Mercedes-Benz cars were sold in the United States by Mercedes-Benz...
Compliance Ranges Comparison
Metalsa
Mercedes-Benz USA
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Metalsa in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
Mercedes-Benz USA has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Metalsa (X = Date, Y = Severity)
Metalsa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mercedes-Benz USA (X = Date, Y = Severity)
Mercedes-Benz USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Metalsa
Mercedes-Benz 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: *.*.