Comparison Overview
Babcock Canada Inc.
Babcock Canada Inc.
800-75 Albert, Ottawa, Ontario, K1P 5E7, CA
Last Update: 02/02/2026
Operating in Canada since 2008, Babcock Canada (Babcock) is a wholly owned subsidiary of Babcock International Group, a global defence, aerospace, and security company. For over 16 years, Babcock has been proud to play a critical role in supporting Canada’s safety and s...
General Dynamics
11011 Sunset Hills Rd, Reston, 20190, US
Last Update: 14/09/2026
From Gulfstream business jets and combat vehicles to nuclear-powered submarines and communications systems, people around the world depend on our products and services for their safety and security. General Dynamics is headquartered in Reston, Virginia, and employs ove...
Compliance Ranges Comparison
Babcock Canada Inc.
General Dynamics
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Babcock Canada Inc. in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
General Dynamics has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Babcock Canada Inc. (X = Date, Y = Severity)
Babcock Canada Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - General Dynamics (X = Date, Y = Severity)
General Dynamics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Babcock Canada Inc.
General Dynamics
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.