Comparison Overview
Jacobs
Jacobs
1999 Bryan Street, Suite 1200, Dallas, 75201, US
Last Update: 11/09/2026
At Jacobs, we're challenging today to reinvent tomorrow – delivering outcomes and solutions for the world's most complex challenges. With a team of approximately 45,000, we provide end-to-end services in advanced manufacturing, cities & places, energy, environmental, li...
EY-Parthenon
1 More London Place, London, SE1 2AF, GB
Last Update: 29/03/2026
Our unique combination of transformative strategy, transactions and corporate finance delivers real-world value – solutions that work in practice, not just on paper. Benefiting from EY’s full spectrum of services, we’ve reimagined strategic consulting to work in a worl...
Compliance Ranges Comparison
Jacobs
EY-Parthenon
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Jacobs in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for EY-Parthenon in 2026.
Incident History - Jacobs (X = Date, Y = Severity)
Jacobs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EY-Parthenon (X = Date, Y = Severity)
EY-Parthenon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Jacobs
EY-Parthenon
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.