Comparison Overview
Schrader Pacific Advanced Valves
Schrader Pacific Advanced Valves
48, Rue de Salins, None, Pontarlier, Bourgogne-Franche-Comté, FR, 25300
Last Update: 24/03/2026
C’est au cœur du Haut-Doubs (25), dans un cadre de vie préservé, réputé pour ses activités de pleine nature, riche pour son tissu industriel et son savoir-faire centré autour de la microtechnique, que notre aventure industrielle a été lancée, en 1898. Leader sur le marc...
Valeo
100, Rue de Courcelles, Paris, Île-de-France, FR, 75017
Last Update: 02/04/2026
Valeo is a technology company and partner to all automakers and new mobility players worldwide. Valeo innovates to make mobility safer, smarter and more sustainable. Valeo enjoys technological and industrial leadership in electrification, driving assistance systems, rei...
Compliance Ranges Comparison
Schrader Pacific Advanced Valves
Valeo
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Parts Manufacturing Industry Avg (This Year)
No incidents recorded for Schrader Pacific Advanced Valves in 2026.
Incidents vs Motor Vehicle Parts Manufacturing Industry Avg (This Year)
No incidents recorded for Valeo in 2026.
Incident History - Schrader Pacific Advanced Valves (X = Date, Y = Severity)
Schrader Pacific Advanced Valves cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Valeo (X = Date, Y = Severity)
Valeo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Schrader Pacific Advanced Valves
Valeo
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: *.*.