Comparison Overview
Volker Staal en Funderingen

Volker Staal en Funderingen
Donker Duyvisweg 75, Dordrecht, Zuid-Holland, 3316, NL
Last Update: 23/04/2026
For many years, Volker Staal en Funderingen (VSF) has worked in the steel fabrication and foundation sectors in Europe. The company specialises in heavy and complex steel structures and foundation techniques. VSF, and its parent company, infrastructure specialist Van ...

Parsons Corporation
14291 Park Meadow Dr, Chantilly, Virginia, US, 20151
Last Update: 04/04/2026
Founded in 1944, Parsons Corporation, a digitally enabled solutions provider, is focused on creating the future of the defense, intelligence, and critical infrastructure markets. From Earth to outer space, we deliver tomorrow’s solutions today. Equipped with the capabil...
Compliance Ranges Comparison

Volker Staal en Funderingen







Parsons Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Volker Staal en Funderingen in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Parsons Corporation in 2026.
Incident History - Volker Staal en Funderingen (X = Date, Y = Severity)
Volker Staal en Funderingen cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Parsons Corporation (X = Date, Y = Severity)
Parsons Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Volker Staal en Funderingen

Parsons Corporation
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: *.*.