Comparison Overview
Van Agtmaal B.V.

Van Agtmaal B.V.
Veilingweg 1, OUDENBOSCH, 4731CW, NL
Last Update: 13/11/2025
Aannemersbedrijf Van Agtmaal vindt haar oorsprong in het Noord-Brabantse Oudenbosch waar het in 1933 werd opgericht door de broers Janus en Cees van Agtmaal. Vanaf de start van het bedrijf profileren wij ons als veelzijdige en deskundige ontwikkelende aannemer in Zuidwe...

NCC
Herrjärva Torg 4, Stockholm, Solna, SE, 170 67
Last Update: 30/03/2026
NCC is one of the leading construction companies in the Nordics. Based on its expertise in managing complex construction processes, NCC contributes to a positive impact of construction for its customers and society. NCC is one of the largest players in the Nordic cons...
Compliance Ranges Comparison

Van Agtmaal B.V.







NCC






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Van Agtmaal B.V. in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for NCC in 2026.
Incident History - Van Agtmaal B.V. (X = Date, Y = Severity)
Van Agtmaal B.V. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NCC (X = Date, Y = Severity)
NCC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Van Agtmaal B.V.

NCC
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: *.*.