Comparison Overview
Bureau Stedelijke Planning (part of Sweco)
Bureau Stedelijke Planning (part of Sweco)
De Holle Bilt 22, De Bilt, Utrecht, 3732 HM, NL
Last Update: 21/04/2026
Bureau Stedelijke Planning is business unit Stedelijke Planning bij Sweco sinds 16 september 2022. Sweco ontwerpt en ontwikkelt de duurzame samenlevingen en de steden van de toekomst. Als business unit Stedelijke Planning blijven we met veel plezier en trots werken aan ...
SM Supermalls
Mall of Asia Complex, Pasay City, 1300, PH
Last Update: 02/04/2026
The SM Group of companies stands today as an institution, a store, a mall, a bank, a home, a resort, a hotel, and a place to see and experience with the family. One of the core business areas of the SM Group is the Shopping Center Management Corporation, generally ref...
Compliance Ranges Comparison
Bureau Stedelijke Planning (part of Sweco)
SM Supermalls
Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Bureau Stedelijke Planning (part of Sweco) in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for SM Supermalls in 2026.
Incident History - Bureau Stedelijke Planning (part of Sweco) (X = Date, Y = Severity)
Bureau Stedelijke Planning (part of Sweco) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SM Supermalls (X = Date, Y = Severity)
SM Supermalls cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bureau Stedelijke Planning (part of Sweco)
SM Supermalls
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: *.*.