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
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout