Comparison Overview
PwC Acceleration Center Kuala Lumpur
PwC Acceleration Center Kuala Lumpur
Jalan Rakyat, Kuala Lumpur City, 50470, MY
Last Update: 20/03/2026
PwC Acceleration Center Kuala Lumpur refers to PricewaterhouseCoopers Service Delivery Center (Malaysia) Sdn. Bhd. PwC Acceleration Center Kuala Lumpur (AC Kuala Lumpur) is part of the network of PwC’s diverse, global talent hubs focused on enabling growth for the or...
Sweco
Gjörwellsgatan 22, Stockholm, 112 60, SE
Last Update: 02/04/2026
Sweco is at the heart of the green transition - planning and designing the sustainable communities and cities of the future. Together with our clients and the collective knowledge of our 23,000 architects, engineers and other specialists, we co-create solutions to addre...
Compliance Ranges Comparison
PwC Acceleration Center Kuala Lumpur
Sweco
Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for PwC Acceleration Center Kuala Lumpur in 2026.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for Sweco in 2026.
Incident History - PwC Acceleration Center Kuala Lumpur (X = Date, Y = Severity)
PwC Acceleration Center Kuala Lumpur cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sweco (X = Date, Y = Severity)
Sweco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PwC Acceleration Center Kuala Lumpur
Sweco
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: *.*.