Comparison Overview
PwC Kazakhstan
PwC Kazakhstan
34 Al-Farabi Avenue, Almaty, undefined, 050059, KZ
Last Update: 04/03/2026
PwC Kazakhstan provides industry-focused assurance, tax, legal and advisory services to various industries. PwC has worked in Kazakhstan for over 30 years since 1993. PwC is a leading professional services organization in the world, ranking first or second in every mark...
ZS
1560 Sherman Avenue, Evanston, IL, US, 60201
Last Update: 07/09/2026
ZS is a management consulting and technology firm that partners with companies to improve life and how we live it. We transform ideas into impact by bringing together data, science, technology and human ingenuity to deliver better outcomes for all. Founded in 1983, ZS h...
Compliance Ranges Comparison
PwC Kazakhstan
ZS
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for PwC Kazakhstan in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for ZS in 2026.
Incident History - PwC Kazakhstan (X = Date, Y = Severity)
PwC Kazakhstan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ZS (X = Date, Y = Severity)
ZS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PwC Kazakhstan
ZS
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.