Comparison Overview
VDL Assembly
VDL Assembly
Handelsweg 21, Hapert, 5527 AL, NL
Last Update: 22/03/2026
VDL Assembly is een systeemleverancier op het gebied van (complexe) medische, optische mechatronische modules en producten. Verder heeft VDL Assembly ervaring in het assembleren van filter- en tankinstallaties voor de agrarische en chemische industrie. VDL Assembly heef...
Rodan + Fields
60 Spear Street, San Francisco, CA, US, 94105
Last Update: 04/04/2026
We are Rodan + Fields, founded by Stanford-trained dermatologists with a mission to revolutionize skincare for women everywhere. Our products are dermatologist-developed and inspired by Women-Backed Science™, delivering real, visible results. We understand what works f...
Compliance Ranges Comparison
VDL Assembly
Rodan + Fields
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for VDL Assembly in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Rodan + Fields in 2026.
Incident History - VDL Assembly (X = Date, Y = Severity)
VDL Assembly cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rodan + Fields (X = Date, Y = Severity)
Rodan + Fields cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
VDL Assembly
Rodan + Fields
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: *.*.