Comparison Overview
Defence Relationship Management (DRM)

Defence Relationship Management (DRM)
51-61 Clifton Street, London, EC2A 4EY, GB
Last Update: 02/04/2026
Defence Relationship Management (DRM) partners with organisations throughout the UK, helping them understand the value of signing the Armed Forces Covenant and building mutually beneficial partnerships with Defence. It provides support on employing Reservists, veterans...

US Army
1500 Army Navy Dr, Arlington, US
Last Update: 31/03/2026
Welcome to the official U.S. Army LinkedIn page. The U.S. Army’s mission is to fight and win our Nation’s wars by providing prompt, sustained land dominance across the full range of military operations and spectrum of conflict in support of combatant commanders. If y...
Compliance Ranges Comparison

Defence Relationship Management (DRM)







US Army






Benchmark & Cyber Underwriting Signals
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for Defence Relationship Management (DRM) in 2026.
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for US Army in 2026.
Incident History - Defence Relationship Management (DRM) (X = Date, Y = Severity)
Defence Relationship Management (DRM) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - US Army (X = Date, Y = Severity)
US Army cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Defence Relationship Management (DRM)

US Army
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