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...
Lockheed Martin
6801 Rockledge Drive, Bethesda, 20817, US
Last Update: 11/09/2026
The world relies on what we do. Headquartered in Bethesda, Maryland, with offices across the U.S. and around the globe, our team delivers solutions that strengthen national security, shape industries and push engineering and technology to new levels. We collaborate t...
Compliance Ranges Comparison
Babcock Canada Inc.
Lockheed Martin
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)
Lockheed Martin has 96.08% more 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 - Lockheed Martin (X = Date, Y = Severity)
Lockheed Martin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Babcock Canada Inc.
Lockheed Martin
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