Comparison Overview
PwC Serbia
PwC Serbia
Omladinskih brigada 88a, Belgrade, 11070, RS
Last Update: 24/12/2025
PwC Serbia was established in Belgrade in 2001. Our Belgrade office currently employs over 298 people, both locals and expatriates. Engagements in Serbia are generally staffed by a combination of local specialists, with knowledge of local conditions and regulations, a...
BDO USA
330 N Wabash Ave, Chicago, IL, US, 60611
Last Update: 01/04/2026
At BDO, our success is measured by what we achieve together. As a leading provider of audit, tax, and advisory services, we put people first cultivating a conscious, caring corporate culture that empowers our professionals and clients to thrive. Our commitment to excell...
Compliance Ranges Comparison
PwC Serbia
BDO USA
Benchmark & Cyber Underwriting Signals
Incidents vs Accounting Industry Avg (This Year)
No incidents recorded for PwC Serbia in 2026.
Incidents vs Accounting Industry Avg (This Year)
No incidents recorded for BDO USA in 2026.
Incident History - PwC Serbia (X = Date, Y = Severity)
PwC Serbia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BDO USA (X = Date, Y = Severity)
BDO USA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PwC Serbia
BDO USA
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.